Bug 1350104 - the run-tests-in-vagrant.sh script should exit with an error if tests failed
Summary: the run-tests-in-vagrant.sh script should exit with an error if tests failed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: tests
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
Assignee: Raghavendra Talur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-25 15:32 UTC by Niels de Vos
Modified: 2019-07-02 04:09 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-07-02 04:09:04 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Niels de Vos 2016-06-25 15:32:26 UTC
Description of problem:
When ./run-tests-in-vagrant.sh runs the regression tests, and tests fail, the script does not exit with an error. This makes it impossible for a CI to report the correct result.

Version-Release number of selected component (if applicable):
3.8 and mainline

How reproducible:
100%

Steps to Reproduce:
1. run ./run-tests-in-vagrant.sh --os=centos6
2. see it fail
3. check the return status with: echo $?

Actual results:
Jenkins notes a return value of 0 as SUCCESS

Expected results:
the script should exit with a non-zero value

Additional info:
See the output of this job in the CentOS CI:
  https://ci.centos.org/view/Gluster/job/gluster_run-tests-in-vagrant/10/console

Comment 1 Amar Tumballi 2019-07-02 04:09:04 UTC
We have a good set of regression right now, and in last year or so, never had any one using run-tests-with-vagrant.sh. Inclined towards not working on this.


Note You need to log in before you can comment on or make changes to this bug.