RFR: 7904153: JTReg should include crash log data in the failure node for xml reports [v2]

William Kemper wkemper at openjdk.org
Wed Feb 18 18:06:30 UTC 2026


On Wed, 18 Feb 2026 17:56:32 GMT, William Kemper <wkemper at openjdk.org> wrote:

>> The system we use (AWS CodeBuild) for running JTReg understands Junit/testNG xml files. For failed tests, it makes the text from the `failure` node easy to access from the UI. I appreciate that these xml files already have `system.err` and `system.out` nodes, but the tooling we use doesn't expose the data here (and I cannot change that tooling). Also, the current implementation takes the first section of `stderr` or `stdout`, which is often empty and comes from the `javac` portion of the test run.
>
> William Kemper has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Use the last output for a section to get the failure. Only do this for the failure node

Probably, the Right Thing™ to do would be to have each jtreg `@test` represented as a junit `testsuite` and each `@run` represented as a junit `testcase` with its own status and `system-err` and `system-out` nodes (which is allowed according to https://github.com/testmoapp/junitxml). But that _is_ a much bigger change.

-------------

PR Comment: https://git.openjdk.org/jtreg/pull/316#issuecomment-3922339682


More information about the jtreg-dev mailing list