[aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64
Aleksey Shipilev
shade at redhat.com
Mon Feb 27 09:19:18 UTC 2017
Hi,
On 02/26/2017 02:42 PM, ci_notify at linaro.org wrote:
> This is a summary of the jcstress test results
> ==============================================
>
> The build and test results are cycled every 15 days.
>
> 2017-02-26 pass rate: 6300/6302, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/056/results/
>
> For detailed information on the test output please refer to:
>
> http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/
Who is responsible for configuring jcstress for these runs? I think it still
uses the "old style" configuration via inherited cmdline options, e.g. like this:
$ java -XX:myoption -XX:myoption2 -jar jcstress.jar ...
This wrecks up the newer jcstress configuration that chooses the VM modes to
test on automatically. See for example:
http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/056/results/org.openjdk.jcstress.tests.volatiles.VolatileIncrementAtomicityTest.html
All of these run with -XX:TieredStopAtLevel=1 (inherited from cmdline,
probably), even when configuration is supposed to be changed (see the trailing
cmdline options).
Please drop the cmdline options, and let jcstress do its job:
$ java -jar jcstress.jar
Thanks,
-Aleksey
More information about the aarch64-port-dev
mailing list