JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64
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/2017/060/... ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/13 pass: 1,266; fail: 25; error: 86 Build 1: aarch64/2017/jan/14 pass: 1,296; fail: 24; error: 57 Build 2: aarch64/2017/jan/23 pass: 1,368; fail: 4; error: 5 Build 3: aarch64/2017/jan/24 pass: 1,367; fail: 5; error: 5 Build 4: aarch64/2017/jan/25 pass: 1,367; fail: 5; error: 5 Build 5: aarch64/2017/jan/29 pass: 1,368; fail: 4; error: 5 Build 6: aarch64/2017/jan/30 pass: 1,366; fail: 5; error: 6 Build 7: aarch64/2017/jan/31 pass: 1,364; fail: 5; error: 8 Build 8: aarch64/2017/feb/01 pass: 1,359; fail: 11; error: 7 Build 9: aarch64/2017/feb/02 pass: 1,358; fail: 10; error: 9 Build 10: aarch64/2017/feb/21 pass: 1,378; fail: 4 Build 11: aarch64/2017/feb/22 pass: 1,378; fail: 4 Build 12: aarch64/2017/feb/25 pass: 1,386; fail: 5 Build 13: aarch64/2017/feb/28 pass: 1,386; fail: 5 Build 14: aarch64/2017/mar/01 pass: 1,387; fail: 5 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/14 pass: 7,234; fail: 630; error: 62 Build 1: aarch64/2017/jan/22 pass: 7,234; fail: 630; error: 62 Build 2: aarch64/2017/jan/23 pass: 7,271; fail: 628; error: 24 Build 3: aarch64/2017/jan/24 pass: 7,269; fail: 641; error: 25 Build 4: aarch64/2017/jan/25 pass: 7,263; fail: 652; error: 22 Build 5: aarch64/2017/jan/29 pass: 7,278; fail: 639; error: 23 Build 6: aarch64/2017/jan/30 pass: 7,300; fail: 614; error: 26 Build 7: aarch64/2017/jan/31 pass: 7,292; fail: 620; error: 29 Build 8: aarch64/2017/feb/01 pass: 7,278; fail: 643; error: 23 Build 9: aarch64/2017/feb/02 pass: 7,294; fail: 622; error: 28 Build 10: aarch64/2017/feb/21 pass: 7,224; fail: 715; error: 20 Build 11: aarch64/2017/feb/22 pass: 7,226; fail: 714; error: 19 Build 12: aarch64/2017/feb/25 pass: 7,266; fail: 705; error: 20 Build 13: aarch64/2017/feb/28 pass: 7,274; fail: 695; error: 23 Build 14: aarch64/2017/mar/01 pass: 7,264; fail: 711; error: 17 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/14 pass: 3,806; error: 17 Build 1: aarch64/2017/jan/22 pass: 3,806; error: 17 Build 2: aarch64/2017/jan/23 pass: 3,820; fail: 1; error: 11 Build 3: aarch64/2017/jan/24 pass: 3,825; fail: 1; error: 6 Build 4: aarch64/2017/jan/25 pass: 3,827; fail: 1; error: 6 Build 5: aarch64/2017/jan/29 pass: 3,829; fail: 1; error: 8 Build 6: aarch64/2017/jan/30 pass: 3,828; fail: 3; error: 7 Build 7: aarch64/2017/jan/31 pass: 3,827; fail: 2; error: 9 Build 8: aarch64/2017/feb/01 pass: 3,825; fail: 6; error: 10 Build 9: aarch64/2017/feb/02 pass: 3,815; fail: 17; error: 10 Build 10: aarch64/2017/feb/21 pass: 3,861 Build 11: aarch64/2017/feb/22 pass: 3,859; error: 2 Build 12: aarch64/2017/feb/25 pass: 3,859; error: 4 Build 13: aarch64/2017/feb/28 pass: 3,861; error: 2 Build 14: aarch64/2017/mar/01 pass: 3,862; error: 2 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/14 pass: 1,294; fail: 27; error: 59 Build 1: aarch64/2017/jan/22 pass: 1,294; fail: 27; error: 59 Build 2: aarch64/2017/jan/23 pass: 1,367; fail: 8; error: 5 Build 3: aarch64/2017/jan/24 pass: 1,367; fail: 7; error: 6 Build 4: aarch64/2017/jan/25 pass: 1,364; fail: 7; error: 9 Build 5: aarch64/2017/jan/29 pass: 1,364; fail: 7; error: 9 Build 6: aarch64/2017/jan/30 pass: 1,364; fail: 7; error: 9 Build 7: aarch64/2017/jan/31 pass: 1,364; fail: 7; error: 9 Build 8: aarch64/2017/feb/01 pass: 1,358; fail: 13; error: 9 Build 9: aarch64/2017/feb/02 pass: 1,273; fail: 61; error: 9 Build 10: aarch64/2017/feb/21 pass: 1,380; fail: 5 Build 11: aarch64/2017/feb/22 pass: 1,378; fail: 6; error: 1 Build 12: aarch64/2017/feb/25 pass: 1,389; fail: 5 Build 13: aarch64/2017/feb/28 pass: 1,388; fail: 6 Build 14: aarch64/2017/mar/01 pass: 1,390; fail: 5 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/14 pass: 7,240; fail: 624; error: 62 Build 1: aarch64/2017/jan/22 pass: 7,240; fail: 624; error: 62 Build 2: aarch64/2017/jan/23 pass: 7,278; fail: 622; error: 23 Build 3: aarch64/2017/jan/24 pass: 7,253; fail: 642; error: 40 Build 4: aarch64/2017/jan/25 pass: 7,283; fail: 628; error: 26 Build 5: aarch64/2017/jan/29 pass: 7,259; fail: 658; error: 23 Build 6: aarch64/2017/jan/30 pass: 7,300; fail: 614; error: 26 Build 7: aarch64/2017/jan/31 pass: 7,258; fail: 613; error: 50 Build 8: aarch64/2017/feb/01 pass: 7,293; fail: 626; error: 25 Build 9: aarch64/2017/feb/02 pass: 7,282; fail: 641; error: 21 Build 10: aarch64/2017/feb/21 pass: 7,223; fail: 718; error: 18 Build 11: aarch64/2017/feb/22 pass: 7,235; fail: 707; error: 17 Build 12: aarch64/2017/feb/25 pass: 7,279; fail: 694; error: 18 Build 13: aarch64/2017/feb/28 pass: 7,265; fail: 708; error: 19 Build 14: aarch64/2017/mar/01 pass: 7,266; fail: 710; error: 16 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/14 pass: 3,800; error: 23 Build 1: aarch64/2017/jan/22 pass: 3,800; error: 23 Build 2: aarch64/2017/jan/23 pass: 3,825; error: 7 Build 3: aarch64/2017/jan/24 pass: 3,824; error: 8 Build 4: aarch64/2017/jan/25 pass: 3,824; fail: 1; error: 9 Build 5: aarch64/2017/jan/29 pass: 3,831; error: 7 Build 6: aarch64/2017/jan/30 pass: 3,827; error: 11 Build 7: aarch64/2017/jan/31 pass: 3,830; fail: 1; error: 7 Build 8: aarch64/2017/feb/01 pass: 3,826; fail: 6; error: 9 Build 9: aarch64/2017/feb/02 pass: 3,834; error: 8 Build 10: aarch64/2017/feb/21 pass: 3,859; error: 2 Build 11: aarch64/2017/feb/22 pass: 3,858; error: 3 Build 12: aarch64/2017/feb/25 pass: 3,860; error: 3 Build 13: aarch64/2017/feb/28 pass: 3,862; error: 1 Build 14: aarch64/2017/mar/01 pass: 3,860; error: 4 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.05x Relative performance: Server critical-jOPS (nc): 0.86x 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: 72.02, Server: 110.27 Client 72.02 / Client 2014-04-01 (43.00): 1.67x 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/jdk9/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2017-01-14 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/013/results/ 2017-01-15 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/014/results/ 2017-01-24 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/023/results/ 2017-01-25 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/024/results/ 2017-01-27 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/025/results/ 2017-01-30 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/029/results/ 2017-02-01 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/030/results/ 2017-02-02 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/031/results/ 2017-02-03 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/032/results/ 2017-02-05 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/033/results/ 2017-02-22 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/052/results/ 2017-02-23 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/053/results/ 2017-02-26 pass rate: 6300/6302, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/056/results/ 2017-03-01 pass rate: 6300/6303, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/059/results/ 2017-03-02 pass rate: 10525/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/060/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/
Question about the jcstress failures 3/2/2017. Aleksey's C1 fix got pushed to jdk9/hs on 3/1/2017. I am assuming that these tests are using JDK9 build from jdk9/dev? So it doesn't have the fix yet? Thanks! - Derek -----Original Message----- From: aarch64-port-dev [mailto:aarch64-port-dev-bounces@openjdk.java.net] On Behalf Of ci_notify@linaro.org Sent: Thursday, March 02, 2017 3:05 PM To: stuart.monteith@linaro.org; fathi.boudra@linaro.org; aarch64-port-dev@openjdk.java.net Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 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/2017/060/... ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/13 pass: 1,266; fail: 25; error: 86 Build 1: aarch64/2017/jan/14 pass: 1,296; fail: 24; error: 57 Build 2: aarch64/2017/jan/23 pass: 1,368; fail: 4; error: 5 Build 3: aarch64/2017/jan/24 pass: 1,367; fail: 5; error: 5 Build 4: aarch64/2017/jan/25 pass: 1,367; fail: 5; error: 5 Build 5: aarch64/2017/jan/29 pass: 1,368; fail: 4; error: 5 Build 6: aarch64/2017/jan/30 pass: 1,366; fail: 5; error: 6 Build 7: aarch64/2017/jan/31 pass: 1,364; fail: 5; error: 8 Build 8: aarch64/2017/feb/01 pass: 1,359; fail: 11; error: 7 Build 9: aarch64/2017/feb/02 pass: 1,358; fail: 10; error: 9 Build 10: aarch64/2017/feb/21 pass: 1,378; fail: 4 Build 11: aarch64/2017/feb/22 pass: 1,378; fail: 4 Build 12: aarch64/2017/feb/25 pass: 1,386; fail: 5 Build 13: aarch64/2017/feb/28 pass: 1,386; fail: 5 Build 14: aarch64/2017/mar/01 pass: 1,387; fail: 5 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/14 pass: 7,234; fail: 630; error: 62 Build 1: aarch64/2017/jan/22 pass: 7,234; fail: 630; error: 62 Build 2: aarch64/2017/jan/23 pass: 7,271; fail: 628; error: 24 Build 3: aarch64/2017/jan/24 pass: 7,269; fail: 641; error: 25 Build 4: aarch64/2017/jan/25 pass: 7,263; fail: 652; error: 22 Build 5: aarch64/2017/jan/29 pass: 7,278; fail: 639; error: 23 Build 6: aarch64/2017/jan/30 pass: 7,300; fail: 614; error: 26 Build 7: aarch64/2017/jan/31 pass: 7,292; fail: 620; error: 29 Build 8: aarch64/2017/feb/01 pass: 7,278; fail: 643; error: 23 Build 9: aarch64/2017/feb/02 pass: 7,294; fail: 622; error: 28 Build 10: aarch64/2017/feb/21 pass: 7,224; fail: 715; error: 20 Build 11: aarch64/2017/feb/22 pass: 7,226; fail: 714; error: 19 Build 12: aarch64/2017/feb/25 pass: 7,266; fail: 705; error: 20 Build 13: aarch64/2017/feb/28 pass: 7,274; fail: 695; error: 23 Build 14: aarch64/2017/mar/01 pass: 7,264; fail: 711; error: 17 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/14 pass: 3,806; error: 17 Build 1: aarch64/2017/jan/22 pass: 3,806; error: 17 Build 2: aarch64/2017/jan/23 pass: 3,820; fail: 1; error: 11 Build 3: aarch64/2017/jan/24 pass: 3,825; fail: 1; error: 6 Build 4: aarch64/2017/jan/25 pass: 3,827; fail: 1; error: 6 Build 5: aarch64/2017/jan/29 pass: 3,829; fail: 1; error: 8 Build 6: aarch64/2017/jan/30 pass: 3,828; fail: 3; error: 7 Build 7: aarch64/2017/jan/31 pass: 3,827; fail: 2; error: 9 Build 8: aarch64/2017/feb/01 pass: 3,825; fail: 6; error: 10 Build 9: aarch64/2017/feb/02 pass: 3,815; fail: 17; error: 10 Build 10: aarch64/2017/feb/21 pass: 3,861 Build 11: aarch64/2017/feb/22 pass: 3,859; error: 2 Build 12: aarch64/2017/feb/25 pass: 3,859; error: 4 Build 13: aarch64/2017/feb/28 pass: 3,861; error: 2 Build 14: aarch64/2017/mar/01 pass: 3,862; error: 2 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/14 pass: 1,294; fail: 27; error: 59 Build 1: aarch64/2017/jan/22 pass: 1,294; fail: 27; error: 59 Build 2: aarch64/2017/jan/23 pass: 1,367; fail: 8; error: 5 Build 3: aarch64/2017/jan/24 pass: 1,367; fail: 7; error: 6 Build 4: aarch64/2017/jan/25 pass: 1,364; fail: 7; error: 9 Build 5: aarch64/2017/jan/29 pass: 1,364; fail: 7; error: 9 Build 6: aarch64/2017/jan/30 pass: 1,364; fail: 7; error: 9 Build 7: aarch64/2017/jan/31 pass: 1,364; fail: 7; error: 9 Build 8: aarch64/2017/feb/01 pass: 1,358; fail: 13; error: 9 Build 9: aarch64/2017/feb/02 pass: 1,273; fail: 61; error: 9 Build 10: aarch64/2017/feb/21 pass: 1,380; fail: 5 Build 11: aarch64/2017/feb/22 pass: 1,378; fail: 6; error: 1 Build 12: aarch64/2017/feb/25 pass: 1,389; fail: 5 Build 13: aarch64/2017/feb/28 pass: 1,388; fail: 6 Build 14: aarch64/2017/mar/01 pass: 1,390; fail: 5 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/14 pass: 7,240; fail: 624; error: 62 Build 1: aarch64/2017/jan/22 pass: 7,240; fail: 624; error: 62 Build 2: aarch64/2017/jan/23 pass: 7,278; fail: 622; error: 23 Build 3: aarch64/2017/jan/24 pass: 7,253; fail: 642; error: 40 Build 4: aarch64/2017/jan/25 pass: 7,283; fail: 628; error: 26 Build 5: aarch64/2017/jan/29 pass: 7,259; fail: 658; error: 23 Build 6: aarch64/2017/jan/30 pass: 7,300; fail: 614; error: 26 Build 7: aarch64/2017/jan/31 pass: 7,258; fail: 613; error: 50 Build 8: aarch64/2017/feb/01 pass: 7,293; fail: 626; error: 25 Build 9: aarch64/2017/feb/02 pass: 7,282; fail: 641; error: 21 Build 10: aarch64/2017/feb/21 pass: 7,223; fail: 718; error: 18 Build 11: aarch64/2017/feb/22 pass: 7,235; fail: 707; error: 17 Build 12: aarch64/2017/feb/25 pass: 7,279; fail: 694; error: 18 Build 13: aarch64/2017/feb/28 pass: 7,265; fail: 708; error: 19 Build 14: aarch64/2017/mar/01 pass: 7,266; fail: 710; error: 16 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/14 pass: 3,800; error: 23 Build 1: aarch64/2017/jan/22 pass: 3,800; error: 23 Build 2: aarch64/2017/jan/23 pass: 3,825; error: 7 Build 3: aarch64/2017/jan/24 pass: 3,824; error: 8 Build 4: aarch64/2017/jan/25 pass: 3,824; fail: 1; error: 9 Build 5: aarch64/2017/jan/29 pass: 3,831; error: 7 Build 6: aarch64/2017/jan/30 pass: 3,827; error: 11 Build 7: aarch64/2017/jan/31 pass: 3,830; fail: 1; error: 7 Build 8: aarch64/2017/feb/01 pass: 3,826; fail: 6; error: 9 Build 9: aarch64/2017/feb/02 pass: 3,834; error: 8 Build 10: aarch64/2017/feb/21 pass: 3,859; error: 2 Build 11: aarch64/2017/feb/22 pass: 3,858; error: 3 Build 12: aarch64/2017/feb/25 pass: 3,860; error: 3 Build 13: aarch64/2017/feb/28 pass: 3,862; error: 1 Build 14: aarch64/2017/mar/01 pass: 3,860; error: 4 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.05x Relative performance: Server critical-jOPS (nc): 0.86x 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: 72.02, Server: 110.27 Client 72.02 / Client 2014-04-01 (43.00): 1.67x 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/jdk9/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2017-01-14 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/013/results/ 2017-01-15 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/014/results/ 2017-01-24 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/023/results/ 2017-01-25 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/024/results/ 2017-01-27 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/025/results/ 2017-01-30 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/029/results/ 2017-02-01 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/030/results/ 2017-02-02 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/031/results/ 2017-02-03 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/032/results/ 2017-02-05 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/033/results/ 2017-02-22 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/052/results/ 2017-02-23 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/053/results/ 2017-02-26 pass rate: 6300/6302, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/056/results/ 2017-03-01 pass rate: 6300/6303, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/059/results/ 2017-03-02 pass rate: 10525/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/060/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/
On 03/02/2017 09:42 PM, White, Derek wrote:
Question about the jcstress failures 3/2/2017.
Aleksey's C1 fix got pushed to jdk9/hs on 3/1/2017. I am assuming that these tests are using JDK9 build from jdk9/dev? So it doesn't have the fix yet?
Seems to be. I added a ton of *.acqrel.* tests in jcstress recently to cover those class of bugs. Hence the failures until that fix propagates. Thanks, -Aleksey
Hi, The automation runs against jdk9/dev, yesterday I confirmed manually that the tests pass with Aleksey's patch applied and don't without. There are a couple of failures apparently in C2 in the following cases: org.openjdk.jcstress.tests.coherence.varHandles.fields.opaque.ShortTest org.openjdk.jcstress.tests.coherence.varHandles.fields.opaque.ByteTest I'm only seeing it occur on one architecture, not ThunderX, and I'm not seeing the CharTest fail. I've been going through various options and the assembler dumps, but so far not gotten to the bottom of it yet. Most recently I tried changing the values for CharTest from 'A' to '\uFFFF', alas, with no luck. BR, Stuart On 02/03/17 20:45, Aleksey Shipilev wrote:
On 03/02/2017 09:42 PM, White, Derek wrote:
Question about the jcstress failures 3/2/2017.
Aleksey's C1 fix got pushed to jdk9/hs on 3/1/2017. I am assuming that these tests are using JDK9 build from jdk9/dev? So it doesn't have the fix yet?
Seems to be. I added a ton of *.acqrel.* tests in jcstress recently to cover those class of bugs. Hence the failures until that fix propagates.
Thanks, -Aleksey
participants (4)
-
Aleksey Shipilev
-
ci_notify＠linaro.org
-
Stuart Monteith
-
White, Derek