To compare stack traces of the matched jobs, you can use the switch --compare-traces. It will generate similar table like with the --compare switch, but instead of Xs, there will be numbers representing stack trace similarity in percentages.
By default, the referential build is the left-most one (or the first), but if you want to change it, you can with --set-referential <jobName:buildNumber> switch.
Example usage: --set-referential "jtreg~tier1-jp17-ojdk17~rpms-el8.x86_64-release.sdk-el8.x86_64.beaker-x11.shenandoah.legacy.lnxagent.jfroff:54"
There is also --cut-trace <head/tail:numberOfCharacters> argument for cutting the test outputs by the numbers specified (to not work with big traces). For example --cut-trace "head:5000" will take a substring of the length 5000 characters from the start of the trace (for EACH test output - it then concats them).
Comparing stack traces
To compare stack traces of the matched jobs, you can use the switch
--compare-traces
. It will generate similar table like with the --compare switch, but instead of Xs, there will be numbers representing stack trace similarity in percentages.By default, the referential build is the left-most one (or the first), but if you want to change it, you can with
--set-referential <jobName:buildNumber>
switch.Example usage:
--set-referential "jtreg~tier1-jp17-ojdk17~rpms-el8.x86_64-release.sdk-el8.x86_64.beaker-x11.shenandoah.legacy.lnxagent.jfroff:54"
There is also
--cut-trace <head/tail:numberOfCharacters>
argument for cutting the test outputs by the numbers specified (to not work with big traces). For example--cut-trace "head:5000"
will take a substring of the length 5000 characters from the start of the trace (for EACH test output - it then concats them).