Red Hat Bugzilla – Bug 1022749
traceback on empty results.xml file
Last modified: 2014-05-21 15:19:02 EDT
Description of problem:
traceback after several hwcert automated tests ran.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run beaker test /distribution/hwcert-client/single test in beaker, reserving afterward to diagnose problems.
2. run hwcert-backend print
$ hwc print
Traceback (most recent call last):
File "/usr/bin/hwcert-backend", line 45, in <module>
success = hwcertBackend.do(args)
File "/usr/share/hwcert/lib/hwcert/backend.py", line 182, in do
result = self.commands[self.command]()
File "/usr/share/hwcert/lib/hwcert/harness.py", line 702, in doPrint
File "/usr/share/hwcert/lib/hwcert/harness.py", line 57, in load
File "/usr/share/hwcert/lib/hwcert/certificationtest.py", line 182, in load
File "/usr/share/hwcert/lib/hwcert/documentbase.py", line 275, in load
self.document = parse(file)
File "/usr/lib64/python2.7/site-packages/_xmlplus/dom/minidom.py", line 1915, in parse
File "/usr/lib64/python2.7/site-packages/_xmlplus/dom/expatbuilder.py", line 930, in parse
result = builder.parseFile(file)
File "/usr/lib64/python2.7/site-packages/_xmlplus/dom/expatbuilder.py", line 211, in parseFile
xml.parsers.expat.ExpatError: no element found: line 1, column 0
output listing hwcert tests planned, passed, or failed.
/var/lock/subsys/hwcert may have already existed, so will post new results after cleaning and trying to reproduce the problem under different conditions.
most other hwcert-backend commands appear to fail with the same traceback.
clean does not fail, but fixes the problem.
I didn't see any errors in the /var/log
two test runs completed with PASS immediately prior
/var/hwcert/results.xml is empty
traceback on the same system. Test results cleaned before this run:
I suspect bug 1022752 caused the empty results.xml, causing this bug.
Created attachment 834217 [details]
Fix the traceback when the xml file is not valid
Created attachment 835025 [details]
Patch V2 Fix the traceback when the xml file is not valid
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.