Initial support for the SPECjbb perf testing benchmark

[ahmedmuhsin]

Initial support for SPECjbb will allow users who already have a licensed local copy of the benchmark to launch a simple run in multi-jvm mode from within aqa-test.

Please see perf/specjbb/README.md for instructions on how to use this feature.

[karianna]

Not sure if shellcheck was run, but if not then that's worth doing so as well.

[gdams]

@smlambert I think this is in a good state now, one initial thought is what would be the best way to skip this when the specJBB material isn’t available? E.g can we skip on Temurin but run elsewhere?

[karianna]

Still a few of my comments left to go, but none are blockers so I'm approving

[Mesbah-Alam]

This PR seems incomplete and it breaks the internal perf test build compilation due to SPECJBB_SRC not being defined (ref: backlog/issues/1051).

From README of this PR :

Set the `SPECJBB_SRC` environment variable to the absolute path of your SPECjbb benchmark directory

This test is assuming ${env.SPECJBB_SRC}/specjbb2015.jar will be pre-staged on the machine where it will run and that SPECJBB_SRC will point to it.

Error detail:

23:03:45  printInput:
23:03:45       [echo] SPECJBB_SRC ${env.SPECJBB_SRC}
23:03:45       [echo] SPECJBB_DEST C:/Users/jenkins/workspace/Test_openjdk8_j9_sanity.perf_x86-32_windows/aqa-tests///..//jvmtest/perf/specjbb/suite
23:03:45       [echo] SPECJBB_JAR specjbb2015.jar
23:03:45       [echo] JAVA_BIN C:/Users/jenkins/workspace/Test_openjdk8_j9_sanity.perf_x86-32_windows/openjdkbinary/j2sdk-image/bin/java
23:03:45  
23:03:45  srcIsValid:
23:03:45       [echo] ##### Validating source SPECjbb dir
23:03:45  
23:03:45  dirIsValid:
23:03:45  
23:03:45  exists:
23:03:45  
23:03:45  isRunnable:
23:03:45       [exec] Error: Unable to access jarfile ${env.SPECJBB_SRC}/specjbb2015.jar
23:03:45       [exec] Result: 1
23:03:45  

[gdams]

@Mesbah-Alam this issue was fixed in 3c48ef4, does IBM have this patch internally?

[Mesbah-Alam]

Hi @gdams , thanks for the info. The failing internal build (launched on March 9th) had missed this fix. Will monitor the next one.