[aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64

Stuart Monteith stuart.monteith at linaro.org
Fri Dec 9 16:41:09 UTC 2016


Hi,
   I've been looking at the JCStress failures, and as far as I can tell,
Andrew's patch on jdk9/hs seems to stop the errors from occurring. They
are a SIGSEGV at variants of the "stlxr x3,x8, [x0]" instruction.


12316:f5689e544d44 rkennke default public
Parent:12315:0be832746ebe 8166719: gc/stress/TestStressG1Humongous.java
fails with OOM...
Child: 12317:3f551de87e59 8169711: CDS does not patch entry trampoline
if intrinsic me...

8169901: AArch64: CompareAndExchange intrinsics clobber address register
Reviewed-by: aph



BR,
	Stuart


On 09/12/16 09:40, ci_notify at linaro.org wrote:
> This is a summary of the JTREG test results
> ===========================================
>  
> The build and test results are cycled every 15 days.
>  
> For detailed information on the test output please refer to: 
>  
>   http://openjdk.linaro.org/jdk9/openjdk-jtreg-nightly-tests/summary/2016/343/summary.html
>  
> -------------------------------------------------------------------------------
> client-release/hotspot
> -------------------------------------------------------------------------------
> Build 0: aarch64/2016/nov/29 pass: 1,310; fail: 10; error: 46
> Build 1: aarch64/2016/nov/30 pass: 1,307; fail: 10; error: 49
> Build 2: aarch64/2016/dec/06 pass: 1,309; fail: 6; error: 52
> Build 3: aarch64/2016/dec/07 pass: 1,309; fail: 6; error: 52
> Build 4: aarch64/2016/dec/08 pass: 1,307; fail: 6; error: 54
> 
> 1 fatal errors were detected; please follow the link above for more detail.
> 
> -------------------------------------------------------------------------------
> client-release/jdk
> -------------------------------------------------------------------------------
> Build 0: aarch64/2016/nov/29 pass: 7,189; fail: 657; error: 42
> Build 1: aarch64/2016/nov/30 pass: 7,187; fail: 650; error: 51
> Build 2: aarch64/2016/dec/08 pass: 7,201; fail: 650; error: 51
> 
> -------------------------------------------------------------------------------
> client-release/langtools
> -------------------------------------------------------------------------------
> Build 0: aarch64/2016/nov/29 pass: 3,759; fail: 1; error: 21
> Build 1: aarch64/2016/nov/30 pass: 3,757; fail: 1; error: 23
> Build 2: aarch64/2016/dec/06 pass: 3,769; fail: 2; error: 17
> Build 3: aarch64/2016/dec/07 pass: 3,771; fail: 1; error: 16
> Build 4: aarch64/2016/dec/08 pass: 3,766; fail: 1; error: 21
> 
> -------------------------------------------------------------------------------
> server-release/hotspot
> -------------------------------------------------------------------------------
> Build 0: aarch64/2016/nov/19 pass: 1,312; fail: 9; error: 48
> Build 1: aarch64/2016/nov/22 pass: 1,316; fail: 9; error: 44
> Build 2: aarch64/2016/nov/24 pass: 1,314; fail: 11; error: 44
> Build 3: aarch64/2016/nov/25 pass: 1,310; fail: 11; error: 48
> Build 4: aarch64/2016/nov/26 pass: 1,310; fail: 11; error: 48
> Build 5: aarch64/2016/nov/28 pass: 1,309; fail: 12; error: 48
> Build 6: aarch64/2016/nov/29 pass: 1,312; fail: 12; error: 45
> Build 7: aarch64/2016/nov/30 pass: 1,309; fail: 12; error: 48
> Build 8: aarch64/2016/dec/06 pass: 1,310; fail: 8; error: 52
> Build 9: aarch64/2016/dec/07 pass: 1,309; fail: 9; error: 52
> Build 10: aarch64/2016/dec/08 pass: 1,309; fail: 8; error: 53
> 
> -------------------------------------------------------------------------------
> server-release/jdk
> -------------------------------------------------------------------------------
> Build 0: aarch64/2016/nov/19 pass: 7,199; fail: 644; error: 38
> Build 1: aarch64/2016/nov/22 pass: 7,202; fail: 636; error: 40
> Build 2: aarch64/2016/nov/24 pass: 7,214; fail: 629; error: 42
> Build 3: aarch64/2016/nov/25 pass: 7,187; fail: 660; error: 38
> Build 4: aarch64/2016/nov/26 pass: 7,226; fail: 619; error: 40
> Build 5: aarch64/2016/nov/28 pass: 7,208; fail: 639; error: 39
> Build 6: aarch64/2016/nov/29 pass: 7,218; fail: 640; error: 30
> Build 7: aarch64/2016/nov/30 pass: 7,206; fail: 643; error: 39
> Build 8: aarch64/2016/dec/08 pass: 7,215; fail: 644; error: 43
> 
> -------------------------------------------------------------------------------
> server-release/langtools
> -------------------------------------------------------------------------------
> Build 0: aarch64/2016/nov/19 pass: 3,736; fail: 2; error: 32
> Build 1: aarch64/2016/nov/22 pass: 3,727; fail: 20; error: 33
> Build 2: aarch64/2016/nov/24 pass: 3,745; fail: 2; error: 33
> Build 3: aarch64/2016/nov/25 pass: 3,748; fail: 1; error: 32
> Build 4: aarch64/2016/nov/26 pass: 3,748; fail: 1; error: 32
> Build 5: aarch64/2016/nov/28 pass: 3,750; fail: 1; error: 30
> Build 6: aarch64/2016/nov/29 pass: 3,752; fail: 1; error: 28
> Build 7: aarch64/2016/nov/30 pass: 3,754; fail: 1; error: 26
> Build 8: aarch64/2016/dec/06 pass: 3,764; fail: 1; error: 23
> Build 9: aarch64/2016/dec/07 pass: 3,764; fail: 1; error: 23
> Build 10: aarch64/2016/dec/08 pass: 3,763; fail: 1; error: 24
> 
> Previous results can be found here: 
>  
>   http://openjdk.linaro.org/jdk9/openjdk-jtreg-nightly-tests/index.html
>  
> 
> SPECjbb2015 composite regression test completed
> ===============================================
> 
> This test measures the relative performance of the server
> compiler running the SPECjbb2015 composite tests and compares
> the performance against the baseline performance of the server
> compiler taken on 2016-11-21.
> 
> In accordance with [1], the SPECjbb2015 tests are run on a system
> which is not production ready and does not meet all the
> requirements for publishing compliant results. The numbers below
> shall be treated as non-compliant (nc) and are for experimental
> purposes only.
> 
> Relative performance: Server max-jOPS (nc): 1.01x
> Relative performance: Server critical-jOPS (nc): 0.92x
> 
> Details of the test setup and historical results may be found here:
> 
>     http://openjdk.linaro.org/jdk9/SPECjbb2015-results/
> 
> [1] http://www.spec.org/fairuse.html#Academic
> 
> Regression test Hadoop-Terasort completed
> =========================================
> 
> This test measures the performance of the server and client compilers
> running Hadoop sorting a 1GB file using Terasort and compares
> the performance against the baseline performance of the Zero interpreter
> and against the baseline performance of the client and server compilers
> on 2014-04-01.
> 
> Relative performance: Zero: 1.0, Client: 73.13, Server: 110.27
> 
> Client 73.13 / Client 2014-04-01 (43.00): 1.70x
> Server 110.27 / Server 2014-04-01 (71.00): 1.55x
> 
> Details of the test setup and historical results may be found here:
> 
>     http://openjdk.linaro.org/9/hadoop-terasort-benchmark-results/
> 
> This is a summary of the jcstress test results
> ==============================================
>  
> The build and test results are cycled every 15 days.
>  
> 2016-11-24 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2016/327/results/
> 2016-11-25 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2016/330/results/
> 2016-11-26 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2016/331/results/
> 2016-12-07 pass rate: 6008/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2016/341/results/
> 2016-12-08 pass rate: 6008/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2016/342/results/
> 2016-12-09 pass rate: 6003/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2016/343/results/
>  
> For detailed information on the test output please refer to: 
>  
>   http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/
>  
> 


More information about the aarch64-port-dev mailing list