You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the plugin will parse, for example, target/surefire-reports/TEST-pkg.Suite.xml once it appears. But if pkg.Suite by itself can take two hours to run (as I have observed for some acceptance-test-harness tests, sadly), you just have no idea from the Jenkins UI what is going on, and the build log does not generally say anything beyond
Running pkg.Suite
So we should pick up the logic from this code and look for any -output.txt without a corresponding TEST-.xml, and display it in a special UI (ideally even a live-update widget).
The text was updated successfully, but these errors were encountered:
Originally reported by @jglick in JENKINS-47208
Currently the plugin will parse, for example,
target/surefire-reports/TEST-pkg.Suite.xmlonce it appears. But ifpkg.Suiteby itself can take two hours to run (as I have observed for some acceptance-test-harness tests, sadly), you just have no idea from the Jenkins UI what is going on, and the build log does not generally say anything beyondRunning
pkg.SuiteSo we should pick up the logic from this code and look for any -output.txt without a corresponding TEST-.xml, and display it in a special UI (ideally even a live-update widget).
The text was updated successfully, but these errors were encountered: