[Piglit] [PATCH] framework/backends/junit: Report expected failures/crashes as skipped.
jfonseca at vmware.com
Tue Mar 3 06:47:59 PST 2015
I recently tried the junit backend's ability to ignore expected
failures/crashes and found it a godsend -- instead of having to look as
test graph results periodically, I can just tell jenkins to email me
when things go south.
The only drawback is that by reporting the expected issues as passing it
makes it too easy to forget about them and misinterpret the pass-rates.
So this change modifies the junit backend to report the expected issues
as skipped, making it more obvious when looking at the test graphs that
these tests are not really passing, and that whatever functionality they
target is not being fully covered.
This change also makes use of the junit `message` attribute to explain
the reason of the skip. (In fact, we could consider using the `message`
attribute on other kind of failures to inform the piglit result, instead
of using the non-standard `type`.)
framework/backends/junit.py | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/framework/backends/junit.py b/framework/backends/junit.py
index 82f9c29..53b6086 100644
@@ -129,17 +129,19 @@ class JUnitBackend(FileBackend):
# Add relevant result value, if the result is pass then it doesn't
# need one of these statuses
if data['result'] == 'skip':
- etree.SubElement(element, 'skipped')
+ res = etree.SubElement(element, 'skipped')
elif data['result'] in ['warn', 'fail', 'dmesg-warn', 'dmesg-fail']:
if expected_result == "failure":
err.text += "\n\nWARN: passing test as an expected failure"
+ res = etree.SubElement(element, 'skipped', message='expected failure')
res = etree.SubElement(element, 'failure')
elif data['result'] == 'crash':
if expected_result == "error":
err.text += "\n\nWARN: passing test as an expected crash"
+ res = etree.SubElement(element, 'skipped', message='expected crash')
res = etree.SubElement(element, 'error')
More information about the Piglit