SBR is now executed exclusively on dedicated MACH5 nodes for OL9 and Windows server 2019, runs take about 10/12 specified using --test-repeat. Announcements are made to the jpg-sbr-announce slack channel.

execution of SBR for JDK23 release cycle
separate sub tasks for each SBR executed on a particular build
The projected duration of each SBR run is 10/12 days

job submission should be from an sbr user on your local machine, to more easily identify the job in mach5

execution of single test execution has become increasingly long with each JDK release such that a repeat of 150 for Windows and 300 will occupy a full 12/14 execution time

job submission examples for Windows and OL9. The parameter --require-machine-attributes "dedicated=corelibs-sbr" schedules the tasks on a dedicated SBR machine in MACH5

Windows 2019:
sh jib.sh mach5 -- remote-test --build-id jdk-24+18 -t open/test/jdk/:tier1,open/test/jdk/:tier2,open/test/jdk/:tier3,closed/test/jdk/:tier2,closed/test/jdk/:tier3 --test-repeat 150 -b windows-x64 --job-type PROMOTED --require-machine-attributes "dedicated=corelibs-sbr" --comment "MACH5 based SBR jdk24 b18" --email mark.sheppard@oracle.com

Linux OL9:
sh jib.sh mach5 -- remote-test --build-id jdk-24+18 -t open/test/jdk/:tier1,open/test/jdk/:tier2,open/test/jdk/:tier3,closed/test/jdk/:tier2,closed/test/jdk/:tier3 --test-repeat 300 -b linux-x64 --job-type PROMOTED --require-machine-attributes "dedicated=corelibs-sbr" --comment "MACH5 based SBR jdk24 b18" --email mark.sheppard@oracle.com