Red Hat Bugzilla – Bug 966723
Hwcert-1.5.9 profiler: passing with forced timer config still fails test
Last modified: 2013-07-31 06:01:43 EDT
Created attachment 752341 [details]
Description of problem:
On RHEL5.8 xen the hwcert test run summary reports the profiler test fails but the profiler output.log reports the test passes(<summary>PASS</summary>).
Version-Release number of selected component (if applicable):
How reproducible: always
Steps to Reproduce:
1. Install RHEL5.8 xen
2. Install hwcert-client-info-1.5.9-28
3. Install hwcert-client-1.5.9-28
4. Run profiler test; hwcert-backend run --test profiler
5. Once test completes display the test run summary; hwcert-backend print
6. The profiler test output.log at /var/log/hwcert/runs/1/profiler/ reports the
test passes which conflicts with the test run summary in step 5.
Actual results: The profiler test run summary and output.log reports conflicting test results.
Expected results: The profiler test run summary and output.log should report the same test status.
Additional info: See attachment for further details.
Created attachment 752799 [details]
output.log from previous attachment - indented
The following sub-sections of the test fail:
<output name="Start Daemon">
Error: oprofiled did not start
"opcontrol --dump" has output on stderr
Note that the last <summary>PASSED</summary> at the end of the log is just indicating the last sub-test passed, not the whole test, so it's not inconsistent.
But, there does appear to be a logical problem in the profiler test. If the daemon won't start, it sets a forced-timer configuration and re-tries the daemon, which the attached logs indicate worked. But the test is still marked as a failure.
Created attachment 752803 [details]
profiler test patch fixing retry logic
Modified the profiler.py file per attached change and the profiler test run summary now reports a pass.
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.