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

Stuart Monteith stuart.monteith at linaro.org
Thu May 31 19:16:07 UTC 2018 

Hi,
 In reference to:
http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/summary/2018/149/summary.html

   As far as I can tell so far, the issues with C1 are caused by:
      8201593: Print array length in ArrayIndexOutOfBoundsException.

Backing out that change was sufficient to cause the failing C1 tests
to pass. Each of the failures in C1 look like they are related to it.
I'm in the process of debugging them.

There is an identical set of failures under hotspot/compiler/aot under
the C1 and C2 test runs. I've not investigated this in any detail yet.

BR,
    Stuart



On 31 May 2018 at 01:53,  <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/jdkX/openjdk-jtreg-nightly-tests/summary/2018/149/summary.html
>
> -------------------------------------------------------------------------------
> client-release/hotspot
> -------------------------------------------------------------------------------
> Build 0: aarch64/2018/mar/31 pass: 1,637; fail: 15; error: 2; not run: 11,615
> Build 1: aarch64/2018/apr/05 pass: 1,672; fail: 15; error: 2; not run: 11,615
> Build 2: aarch64/2018/apr/07 pass: 1,675; fail: 14; error: 2; not run: 11,615
> Build 3: aarch64/2018/apr/15 pass: 1,674; fail: 14; error: 2; not run: 11,615
> Build 4: aarch64/2018/apr/17 pass: 1,675; fail: 14; error: 1; not run: 11,615
> Build 5: aarch64/2018/may/10 pass: 3,190; fail: 14; error: 3; not run: 11,616
> Build 6: aarch64/2018/may/11 pass: 3,192; fail: 12; error: 3; not run: 11,616
> Build 7: aarch64/2018/may/13 pass: 3,191; fail: 13; error: 3; not run: 11,616
> Build 8: aarch64/2018/may/15 pass: 3,234; fail: 34; error: 4; not run: 11,619
> Build 9: aarch64/2018/may/17 pass: 3,263; fail: 34; error: 4; not run: 11,619
> Build 10: aarch64/2018/may/21 pass: 3,769; fail: 38; error: 5; not run: 11,619
> Build 11: aarch64/2018/may/23 pass: 3,868; fail: 37; error: 4; not run: 11,619
> Build 12: aarch64/2018/may/25 pass: 5,209; fail: 45; error: 3; not run: 11,619
> Build 13: aarch64/2018/may/27 pass: 5,210; fail: 43; error: 4; not run: 11,619
> Build 14: aarch64/2018/may/29 pass: 5,209; fail: 44; error: 4; not run: 11,619
>
> 7 fatal errors were detected; please follow the link above for more detail.
>
> -------------------------------------------------------------------------------
> client-release/jdk
> -------------------------------------------------------------------------------
> Build 0: aarch64/2018/mar/31 pass: 7,766; fail: 643; error: 18
> Build 1: aarch64/2018/apr/05 pass: 7,787; fail: 619; error: 21
> Build 2: aarch64/2018/apr/07 pass: 7,781; fail: 632; error: 18
> Build 3: aarch64/2018/apr/15 pass: 7,824; fail: 583; error: 29
> Build 4: aarch64/2018/apr/17 pass: 7,800; fail: 621; error: 15
> Build 5: aarch64/2018/may/10 pass: 7,905; fail: 595; error: 22
> Build 6: aarch64/2018/may/11 pass: 7,880; fail: 623; error: 19
> Build 7: aarch64/2018/may/13 pass: 7,903; fail: 599; error: 23
> Build 8: aarch64/2018/may/15 pass: 7,865; fail: 629; error: 32
> Build 9: aarch64/2018/may/17 pass: 8,329; fail: 595; error: 29
> Build 10: aarch64/2018/may/21 pass: 8,326; fail: 604; error: 25
> Build 11: aarch64/2018/may/23 pass: 8,328; fail: 610; error: 24
> Build 12: aarch64/2018/may/25 pass: 8,302; fail: 638; error: 23
> Build 13: aarch64/2018/may/27 pass: 8,331; fail: 611; error: 23
> Build 14: aarch64/2018/may/29 pass: 8,320; fail: 616; error: 29
>
> 4 fatal errors were detected; please follow the link above for more detail.
>
> -------------------------------------------------------------------------------
> client-release/langtools
> -------------------------------------------------------------------------------
> Build 0: aarch64/2018/mar/31 pass: 3,851; fail: 6
> Build 1: aarch64/2018/apr/05 pass: 3,851; fail: 6
> Build 2: aarch64/2018/apr/07 pass: 3,851; fail: 6; error: 3
> Build 3: aarch64/2018/apr/15 pass: 3,855; fail: 6; error: 3
> Build 4: aarch64/2018/apr/17 pass: 3,856; fail: 6; error: 2
> Build 5: aarch64/2018/may/10 pass: 3,865; fail: 6
> Build 6: aarch64/2018/may/11 pass: 3,865; fail: 6
> Build 7: aarch64/2018/may/13 pass: 3,862; fail: 6; error: 4
> Build 8: aarch64/2018/may/15 pass: 3,863; fail: 6; error: 3
> Build 9: aarch64/2018/may/17 pass: 3,864; fail: 6; error: 3
> Build 10: aarch64/2018/may/21 pass: 3,867; fail: 6; error: 2
> Build 11: aarch64/2018/may/23 pass: 3,871; fail: 6; error: 3
> Build 12: aarch64/2018/may/25 pass: 3,877; fail: 6; error: 5
> Build 13: aarch64/2018/may/27 pass: 3,880; fail: 6; error: 2
> Build 14: aarch64/2018/may/29 pass: 3,879; fail: 6; error: 4
>
> -------------------------------------------------------------------------------
> server-release/hotspot
> -------------------------------------------------------------------------------
> Build 0: aarch64/2018/mar/31 pass: 1,645; fail: 15; error: 1; not run: 11,615
> Build 1: aarch64/2018/apr/05 pass: 1,680; fail: 14; error: 2; not run: 11,615
> Build 2: aarch64/2018/apr/07 pass: 1,685; fail: 13; not run: 11,615
> Build 3: aarch64/2018/apr/15 pass: 1,682; fail: 13; error: 2; not run: 11,615
> Build 4: aarch64/2018/apr/17 pass: 1,682; fail: 14; error: 1; not run: 11,615
> Build 5: aarch64/2018/may/10 pass: 3,199; fail: 12; error: 3; not run: 11,616
> Build 6: aarch64/2018/may/11 pass: 3,199; fail: 12; error: 3; not run: 11,616
> Build 7: aarch64/2018/may/13 pass: 3,200; fail: 11; error: 3; not run: 11,616
> Build 8: aarch64/2018/may/15 pass: 3,243; fail: 33; error: 3; not run: 11,619
> Build 9: aarch64/2018/may/17 pass: 3,274; fail: 31; error: 3; not run: 11,619
> Build 10: aarch64/2018/may/21 pass: 3,783; fail: 34; error: 2; not run: 11,619
> Build 11: aarch64/2018/may/23 pass: 3,879; fail: 34; error: 3; not run: 11,619
> Build 12: aarch64/2018/may/25 pass: 5,219; fail: 42; error: 3; not run: 11,619
> Build 13: aarch64/2018/may/27 pass: 5,220; fail: 40; error: 4; not run: 11,619
> Build 14: aarch64/2018/may/29 pass: 5,219; fail: 42; error: 3; not run: 11,619
>
> 4 fatal errors were detected; please follow the link above for more detail.
>
> -------------------------------------------------------------------------------
> server-release/jdk
> -------------------------------------------------------------------------------
> Build 0: aarch64/2018/mar/31 pass: 7,798; fail: 611; error: 18
> Build 1: aarch64/2018/apr/05 pass: 7,816; fail: 593; error: 18
> Build 2: aarch64/2018/apr/07 pass: 7,797; fail: 619; error: 15
> Build 3: aarch64/2018/apr/15 pass: 7,849; fail: 560; error: 27
> Build 4: aarch64/2018/apr/17 pass: 7,825; fail: 593; error: 18
> Build 5: aarch64/2018/may/10 pass: 7,918; fail: 586; error: 18
> Build 6: aarch64/2018/may/11 pass: 7,912; fail: 592; error: 18
> Build 7: aarch64/2018/may/13 pass: 7,892; fail: 616; error: 17
> Build 8: aarch64/2018/may/15 pass: 7,918; fail: 586; error: 22
> Build 9: aarch64/2018/may/17 pass: 8,349; fail: 587; error: 18
> Build 10: aarch64/2018/may/21 pass: 8,363; fail: 578; error: 15
> Build 11: aarch64/2018/may/23 pass: 8,361; fail: 583; error: 19
> Build 12: aarch64/2018/may/25 pass: 8,357; fail: 591; error: 16
> Build 13: aarch64/2018/may/27 pass: 8,359; fail: 589; error: 18
> Build 14: aarch64/2018/may/29 pass: 8,372; fail: 576; error: 18
>
> -------------------------------------------------------------------------------
> server-release/langtools
> -------------------------------------------------------------------------------
> Build 0: aarch64/2018/mar/31 pass: 3,850; fail: 6; error: 1
> Build 1: aarch64/2018/apr/05 pass: 3,851; fail: 6
> Build 2: aarch64/2018/apr/07 pass: 3,853; fail: 5; error: 2
> Build 3: aarch64/2018/apr/15 pass: 3,854; fail: 6; error: 4
> Build 4: aarch64/2018/apr/17 pass: 3,854; fail: 6; error: 4
> Build 5: aarch64/2018/may/10 pass: 3,862; fail: 6; error: 3
> Build 6: aarch64/2018/may/11 pass: 3,860; fail: 6; error: 5
> Build 7: aarch64/2018/may/13 pass: 3,861; fail: 6; error: 5
> Build 8: aarch64/2018/may/15 pass: 3,858; fail: 6; error: 8
> Build 9: aarch64/2018/may/17 pass: 3,861; fail: 6; error: 6
> Build 10: aarch64/2018/may/21 pass: 3,863; fail: 6; error: 6
> Build 11: aarch64/2018/may/23 pass: 3,867; fail: 6; error: 7
> Build 12: aarch64/2018/may/25 pass: 3,878; fail: 6; error: 4
> Build 13: aarch64/2018/may/27 pass: 3,877; fail: 6; error: 5
> Build 14: aarch64/2018/may/29 pass: 3,877; fail: 6; error: 6
>
> Previous results can be found here:
>
>   http://openjdk.linaro.org/jdkX/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): 0.65x
> Relative performance: Server critical-jOPS (nc): 0.58x
>
> Details of the test setup and historical results may be found here:
>
>     http://openjdk.linaro.org/jdkX/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: 65.35, Server: 103.79
>
> Client 65.35 / Client 2014-04-01 (43.00): 1.52x
> Server 103.79 / Server 2014-04-01 (71.00): 1.46x
>
> Details of the test setup and historical results may be found here:
>
>     http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/
>
> This is a summary of the jcstress test results
> ==============================================
>
> The build and test results are cycled every 15 days.
>
> 2018-03-31 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/090/results/
> 2018-04-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/095/results/
> 2018-04-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/097/results/
> 2018-04-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/105/results/
> 2018-04-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/107/results/
> 2018-05-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/130/results/
> 2018-05-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/131/results/
> 2018-05-14 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/133/results/
> 2018-05-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/135/results/
> 2018-05-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/137/results/
> 2018-05-22 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/141/results/
> 2018-05-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/143/results/
> 2018-05-26 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/145/results/
> 2018-05-28 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/147/results/
> 2018-05-31 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/149/results/
>
> For detailed information on the test output please refer to:
>
>   http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/

More information about the aarch64-port-dev mailing list