Bug 1371654 - ensure that rteval exits with non-zero status when stopping early
Summary: ensure that rteval exits with non-zero status when stopping early
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rteval
Version: 7.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Clark Williams
QA Contact: Jiri Kastner
URL:
Whiteboard:
Depends On:
Blocks: 1274397
TreeView+ depends on / blocked
 
Reported: 2016-08-30 17:49 UTC by Clark Williams
Modified: 2016-11-04 01:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 01:34:53 UTC
Target Upstream Version:

Attachments (Terms of Use)
patch to ensure rteval exits with non-zero status on early exit from test loop (1.69 KB, patch)
2016-08-31 16:40 UTC, Clark Williams 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2244 0 normal SHIPPED_LIVE rteval bug fix and enhancement update 2016-11-03 13:29:41 UTC

Description Clark Williams 2016-08-30 17:49:50 UTC 
Description of problem:

Currently rteval always exits with a zero (success) status. Change this so that when exiting early from the measurement loop, we exit with a non-zero status.
Comment 2 Clark Williams 2016-08-31 16:40:11 UTC 
Created attachment 1196459 [details]
patch to ensure rteval exits with non-zero status on early exit from test loop
Comment 3 Clark Williams 2016-08-31 16:40:37 UTC 
rteval-2.11-1.el7 contains the above patch
Comment 4 Clark Williams 2016-08-31 16:42:03 UTC 
easiest reproducer is to run with --cyclictest-breaktrace and specify a very low threshold value:

$ sudo rteval --duration=10m --cyclictest-breaktrace=5
$ echo "exit value == $?"
1
Comment 8 errata-xmlrpc 2016-11-04 01:34:53 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2244.html
Note You need to log in before you can comment on or make changes to this bug.