Dylan,
I'm not sure you guys are still using the junit backend regularly or
not. Would be the change below OK?
BTW, I finished transition all my jenkins' piglit jobs to the junit backend.
Feel free to remove the summary-junit code, or let me know if you rather
I do it.
Jose
On 20/11/14 12:06, [email protected] wrote:
From: José Fonseca <[email protected]>
Showing the command line of the test is quite useful, specially when
diagnosing failures.
Unfortunately JUnit format allows no better place to have it other than
stdout/stderr.
---
framework/backends/junit.py | 3 +++
1 file changed, 3 insertions(+)
diff --git a/framework/backends/junit.py b/framework/backends/junit.py
index 1c27e98..59d06c6 100644
--- a/framework/backends/junit.py
+++ b/framework/backends/junit.py
@@ -144,6 +144,9 @@ class JUnitBackend(FileBackend):
out = etree.SubElement(element, 'system-out')
out.text = data['out']
+ # Prepend command line to stdout
+ out.text = data['command'] + '\n' + out.text
+
# Add stderr
err = etree.SubElement(element, 'system-err')
err.text = data['err']
_______________________________________________
Piglit mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/piglit
