Hide Forgot
Description of problem: The old kits ended with "exit code 0" in the logs before and after packaging to indicate a passing run. We used this key when reviewing logs to ensure we were submitting passing results. The new kit output.log files no longer has this after packaging. This makes it more difficult to review logs that were run by external teams. Is there something to key on in the logs to verify pass/fail status without submitting results to the website? Version-Release number of selected component (if applicable): v7-1-3-35 / 6.1 snap 5 How reproducible: Everytime Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The v7 print command shows passing status of each test run. The v7 server may also be run on the SUT, and test results formatted via web/css.
Greg What if we are not running the tests and have no access to the SUT at runtime? We are only provided the final rpm for submission.
Hi Gregg, Extracting results.xml from the rpm, and placing it locally will allow v7 print to work. Alternatively the results.xml path can be set in /etc/v7.xml. We can also look @ a 1.4 feature to enable using /var/v7/store directly in v7 which should simplify this and avoid needing a script.
Created attachment 513831 [details] report.py patch to add PASS/FAIL as last line of logs in results rpm
*** Bug 705871 has been marked as a duplicate of this bug. ***
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: In v7 1.3, the exit code after testing running was no longer printed which made it difficult to determine test PASS/FAIL state for user. This issue has been fixed in v7 1.4, now a PASS/FAIL string will be printed after each test execution finishes.
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. http://rhn.redhat.com/errata/RHBA-2011-1436.html