Openj9: jdknext functional sanity tests not running

Created on 1 Mar 2019  路  19Comments  路  Source: eclipse/openj9

https://ci.eclipse.org/openj9/job/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/4

19:02:02  ant -f scripts/build_test.xml -DTEST_ROOT=/home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/test/TestConfig/.. -DBUILD_ROOT=/home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/test/TestConfig/../../jvmtest -DJAVA_BIN=/home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/build/linux-ppc64le-server-release/images/jdk/bin -DJDK_VERSION=8 -DJCL_VERSION=latest -DBUILD_LIST= -DRESOURCES_DIR=/home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/test/TestConfig/../../jvmtest/TestConfig/resources -DPLATFORM=linux_ppcle-64_cr -DJDK_HOME=/home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/build/linux-ppc64le-server-release/images/jdk/bin/../.. -DJVM_VERSION=openjdk8-openj9
19:02:03  Buildfile: /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/test/TestConfig/scripts/build_test.xml
19:02:03       [echo]  JAVA_BIN is /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/build/linux-ppc64le-server-release/images/jdk/bin 
19:02:03       [echo]  build.list is */build.xml 
19:02:03  
19:02:03  -create_test_directory:
19:02:03      [mkdir] Created dir: /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/jvmtest
19:02:03  
19:02:03  stage_test_material:
19:02:03       [copy] Copying 40 files to /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/jvmtest
19:02:03  
19:02:03  build:
19:02:04  
19:02:04  dist_functional:
19:02:04      [mkdir] Created dir: /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/jvmtest/functional
19:02:04       [copy] Copying 2 files to /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/jvmtest/functional
19:02:04  
19:02:04  build_functional:
19:02:04  
19:02:04  build:
19:02:04       [echo] os.name: Linux
19:02:04  
19:02:04  init:
19:02:04      [mkdir] Created dir: /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/jvmtest/functional/DDR_Test
19:02:04      [mkdir] Created dir: /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/test/functional/DDR_Test/bin
19:02:04  
19:02:04  compile:
19:02:04       [echo] Ant version is Apache Ant(TM) version 1.10.5 compiled on July 10 2018
19:02:04       [echo] ============COMPILER SETTINGS============
19:02:04       [echo] ===fork:       yes
19:02:04       [echo] ===executable: /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/build/linux-ppc64le-server-release/images/jdk/bin/../../bin/javac
19:02:04       [echo] ===debug:      on
19:02:04       [echo] ===destdir:    /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/test/TestConfig/../../jvmtest/functional/DDR_Test
19:02:04      [javac] Compiling 51 source files to /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/test/functional/DDR_Test/bin
19:02:04  
19:02:04  BUILD FAILED
19:02:04  /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/test/TestConfig/scripts/build_test.xml:71: The following error occurred while executing this line:
19:02:04  /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/test/functional/build.xml:52: The following error occurred while executing this line:
19:02:04  /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/test/functional/DDR_Test/build.xml:113: The following error occurred while executing this line:
19:02:04  /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/openj9/test/functional/DDR_Test/build.xml:59: Error running /home/jenkins/workspace/PullRequest-Sanity-JDKnext-linux_ppc-64_cmprssptrs_le-OpenJ9/build/linux-ppc64le-server-release/images/jdk/bin/../../bin/javac compiler
19:02:04  
19:02:04  Total time: 1 second
19:02:04  makefile:82: recipe for target 'compile' failed
test jdk-head

Most helpful comment

I think SDK_VERSION is used for our pipelines, its used to set JAVA_VERSION (among other things).
https://github.com/eclipse/openj9/blob/master/buildenv/jenkins/common/variables-functions#L454

00:01:18.085  SDK_VERSION:11
[Pipeline] echo
00:01:18.087  JAVA_VERSION:SE110
00:00:52.501  SDK_VERSION:next
[Pipeline] echo
00:00:52.502  JAVA_VERSION:SEnext0

Probably not what we want :D

All 19 comments

There is no JDK_VERSION passed into test job, so we default to 8.

00:27:57.681  perl testKitGen.pl --graphSpecs=linux_ppc-64_cmprssptrs_le --jdkVersion=8 --impl=openj9 --buildList= --iterations=1 --testFlag= ; \

fyi @AdamBrousseau

What value should we be passing for "next"?

Whatever JDK_VERSION that the user is going to run. I think the user should set it.

We'd like to derive it somehow, so we don't need to keep updating it every 6 months.

For now, I'm setting SDK_VERSION to 13 in the xlinux and plinux sanity jobs.

@AdamBrousseau does SDK_VERSION get passed into test job as JDK_VERSION?

Or is changing the PR jobs useless now, because they are auto generated?

Ok I was slightly confused. These are PR jobs which don't use the Test jobs driven by the Adopt scripts (yet) and aren't auto generated. We don't set JDK_VERSION in our PR jobs, just SDK_VERSION and JAVA_VERSION. How do the tests know now for jdk11 that its 11?

Because right now we support both JAVA_VERSION and its replacement, JDK_VERSION. JAVA_VERSION is deprecated and we will soon remove it from test scripts & TKG (now that most locations have been updated to use JDK_VERSION).

  • What is SDK_VERSION? It is not required by test.
  • Do PR job set JAVA_VERSION as env variable? I do not see JAVA_VERSION in the console output.

I think SDK_VERSION is used for our pipelines, its used to set JAVA_VERSION (among other things).
https://github.com/eclipse/openj9/blob/master/buildenv/jenkins/common/variables-functions#L454

00:01:18.085  SDK_VERSION:11
[Pipeline] echo
00:01:18.087  JAVA_VERSION:SE110
00:00:52.501  SDK_VERSION:next
[Pipeline] echo
00:00:52.502  JAVA_VERSION:SEnext0

Probably not what we want :D

fyi PR for Temporarily support for JAVA_VERSION=SE130
We aim to stop supporting JAVA_VERSION for jdk13+. Please switch to use JDK_VERSION.

@llxia does the above change mean the tests should run now, or does Adam still need to make a change?

My change allows test framework to take JAVA_VERSION=SE130. I think Adam still need to make some changes. As you tried earlier https://github.com/eclipse/openj9/issues/4936#issuecomment-468731650, this jdknext PR build does not work for SDK_VERSION=13.

Also, if we have jdk13 ready somewhere, we can test it using Grinder or any test job with JDK_VERSION set to 13.

We can either land #2836, or if we don't want to wait and I have to make the change anyways, I might as well switch to JDK_VERSION. I was originally hesitant to set next to 13, but once the builds switch, we won't be setting it anymore so I think it's fine.

I'd prefer not to wait on #2836

4951

00:00:55.361  SDK_VERSION:11
[Pipeline] echo
00:00:55.363  JDK_VERSION:11
00:01:20.482  SDK_VERSION:next
[Pipeline] echo
00:01:20.484  JDK_VERSION:13
Was this page helpful?
0 / 5 - 0 ratings

Related issues

Mesbah-Alam picture Mesbah-Alam  路  5Comments

Jeeppler picture Jeeppler  路  5Comments

xliang6 picture xliang6  路  3Comments

pshipton picture pshipton  路  3Comments

mikezhang1234567890 picture mikezhang1234567890  路  5Comments