| === salem_ is now known as _salem | ||
| === yofel_ is now known as yofel | ||
| === Ursinha is now known as Ursinha-afk | ||
| === Ursinha-afk is now known as Ursinha | ||
| jtaylor | can the summary of the jenkins build be displayed directly on the build page? | 11:56 |
|---|---|---|
| jtaylor | e.g. via the standard test result display? | 11:56 |
| jtaylor | right now its hard to say is something actually changed in build that was always failing | 11:57 |
| xnox | we have many different kinds of jobs in jenkins. Can you give an example of what you mean? | 12:04 |
| === _salem is now known as salem_ | ||
| jtaylor | autopkgtest jobs | 12:13 |
| jtaylor | e.g. https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-python-numpy/ | 12:14 |
| jtaylor | its got five tests, one fails | 12:14 |
| jtaylor | what I want to know if when more than one fail | 12:14 |
| jtaylor | which is not immediately visible | 12:14 |
| jtaylor | jenkins can display test failure trend graphs for that | 12:15 |
| jtaylor | you just need to convert the summary.log into a junit xml | 12:15 |
| jtaylor | which is not hard | 12:15 |
| jibel | jtaylor, good idea, could you file a bug against lp:auto-package-testing please | 12:36 |
| jtaylor | bug 1092887 | 12:51 |
| ubot5 | bug 1092887 in Auto Package Testing "display autopkgtest results in jenkins directly" [Undecided,New] https://launchpad.net/bugs/1092887 | 12:51 |
| xnox | aha. Similarly static iso validation "test-suite" should be similarly displayed. | 12:53 |
| === salem_ is now known as _salem | ||
| === _salem is now known as salem_ | ||
| === d_kessel is now known as dkessel | ||
| * dkessel is puzzled | 17:15 | |
| dkessel | ah... much better without my ghost - good evening! | 17:16 |
| === salem_ is now known as _salem | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!