jtreg-andrlosFork8.1+1-jtrfix-crashonly-V01.0

crashonly introduction for 8.1
jtrfix is already in jtreg 7.5 codebase
built using OpenJDK 25.0.1

jtreg-andrlosFork7.5.2+1-jtrfix-crashonly-V01.0

crashonly introduction for jtreg 7.5.2+1 jtreg
jtrfix is already in jtreg 7.5 codebase
built using OpenJDK 17.0.16

jtreg-andrlosFork8.1+1-jtrfix-V01.0

jtrfix alignment for jtrfix releases
jtrfix is already in jtreg 7.5 codebase
identical to 8.1+1 upstream
built using OpenJDK 25.0.1

jtreg-andrlosFork7.5.2+1-jtrfix-V01.0

clean build of jtreg 7.5.2+1
jtrfix is already in jtreg 7.5 codebase, but releasing this in sake of unification
built using OpenJDK 17.0.16

jtreg-andrlosFork7.3.1+2-jtrfix-crashonly-V01.0

now also featuring compilation error fix for jtr.xml logs.. not useful for crashonly variant since crashonly cares only about jvm crashes.. releasing for alignment purposes.

jtreg-andrlosFork7.3.1+2-jtrfix-V01.0

now also featuring compilation error fix for jtr.xml logs

jtreg-andrlosFork6.2-jtrfix-crashonly-V01.0

now also featuring compilation failures in jtr.xml outputs.. there is no purpose for crashonly tho, since crashonly ignores all failures except jvm crashes

jtreg-andrlosFork6.2-jtrfix-V01.0

now featuring also compilation errors in the jtr.xml output

jtreg-andrlosFork7.3.1+1-jtrfix-crashonly-V01.0

Since the upstream jtreg already features my jtrxml fix, the only difference to that is now the feature of crashonly code, so this release is also strictly for fastdebug testing and only reports jvm crashes as failures.

jtreg-andrlosFork7.3.1+1-jtrfix-V01.0

built from the current tip of the jtreg repository, the jtrfix is already in upstream, however did not yet made it to release