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

[William Kemper]

On Wed, 18 Feb 2026 15:02:11 GMT, Jaikiran Pai <jpai at openjdk.org> wrote:

>> 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
>
> src/share/classes/com/sun/javatest/regtest/report/XMLWriter.java line 273:
> 
>> 271:                 line.contains("SIGABRT") || line.contains("problematic frame") ||
>> 272:                 line.contains("Internal Error") || line.contains("fatal error"))) {
>> 273:                 inCrash = true;
> 
> It feels a bit arbitrary that we are looking for this content to detect a test which has caused a JVM crash. In the systems where these jtreg generated XML reports are being used, are the JVM crash files (hs_err...) not being generated? Wouldn't those already have the necessary crash details? I am guessing that even if these 100 odd lines were to be printed out in the XML report, the actual hs_err file would still be needed to understand what caused the crash.

The tests may or may not create an hs_err file depending on how they are configured. Similarly, not every test will put this information on `stdout` or `stderr`. Yes, there will be times when the entire test log and hs_err file will be needed. Though in most such cases, I expect users would ultimately rerun the failed test locally. With this PR, I aim only for a modest experience improvement in systems that readily display the content of the `failure` node (such as AWS CodeBuild).

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

PR Review Comment: https://git.openjdk.org/jtreg/pull/316#discussion_r2823593680