Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jdk11u build pipeline extended system test runs fail #1294

Closed
lumpfish opened this issue Aug 22, 2019 · 8 comments
Closed

jdk11u build pipeline extended system test runs fail #1294

lumpfish opened this issue Aug 22, 2019 · 8 comments
Labels
Milestone

Comments

@lumpfish
Copy link
Contributor

lumpfish commented Aug 22, 2019

All the extended system tests run by the build pipeline for the rerelease of jdk11u on MacOS failed with these messages:

Can't open perl script "/stf/stf.core/scripts/stf.pl": No such file or directory

Looks like something may be wrong with setting the test root directory which should prefix '/stf' in the playlist or testkitgen variables.
Job is https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_extended.system_x86-64_mac/25/console

@lumpfish
Copy link
Contributor Author

The tests execute OK when I reran them as a Test_grinder job: https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/1925/console

@smlambert
Copy link
Contributor

@lumpfish you have shared a link to jdk11 builds (jdk8 looks ok, https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_extended.system_x86-64_mac/22/), should update the title of this issue to match.

FYI @Mesbah-Alam @llxia

@llxia
Copy link
Contributor

llxia commented Aug 22, 2019

@lumpfish lumpfish changed the title jdk8u build pipeline extended system test runs fail jdk11u build pipeline extended system test runs fail Aug 22, 2019
@lumpfish
Copy link
Contributor Author

Sorry - it should all have said jdk11, not jdk8. Updated the title and comments.

Yes, follow on builds are ok, weird a parameter should go 'missing' though.

@smlambert
Copy link
Contributor

that is odd... wonder if there were temporary changes in build pipeline code (maybe should look)? we can keep this open for the next few runs, to make sure its not some strange intermittent behaviour

@sophia-guo
Copy link
Contributor

sophia-guo commented Aug 23, 2019

Looks like build workspace is not clean https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_extended.system_x86-64_mac/25/console

10:40:46  clean:
10:40:46     [delete] Deleting: /Users/jenkins/workspace/Test_openjdk11_j9_extended.system_x86-64_mac/openjdk-tests/TestConfig/autoGenEnv.mk
10:40:46     [delete] Deleting directory /Users/jenkins/workspace/Test_openjdk11_j9_extended.system_x86-64_mac/openjdk-tests/TestConfig/src/bin
10:40:46     [delete] Deleting: /Users/jenkins/workspace/Test_openjdk11_j9_extended.system_x86-64_mac/openjdk-tests/TestConfig/src/EnvDetector.jar

In a clean build there shouldn't be any files.

My guess is because of this TEST AUTO GEN wasn't SUCCESSFUL.

10:42:52  Generating make file /Users/jenkins/workspace/Test_openjdk11_j9_extended.system_x86-64_mac/openjdk-tests/TestConfig/scripts/testKitGen/../../../system/sharedClasses/autoGen.mk
10:42:52  
10:42:52  Generating make file /Users/jenkins/workspace/Test_openjdk11_j9_extended.system_x86-64_mac/openjdk-tests/TestConfig/scripts/testKitGen/../../../system/autoGen.mk
10:42:52  
10:42:52  Generating make file /Users/jenkins/workspace/Test_openjdk11_j9_extended.system_x86-64_mac/openjdk-tests/TestConfig/scripts/testKitGen/../../../systemtest/openj9-systemtest/openj9.build/autoGen.mk
10:42:52  perl scripts/tools/getDependencies.pl -path '/Users/jenkins/workspace/Test_openjdk11_j9_extended.system_x86-64_mac/openjdk-tests/TestConfig/../TestConfig/lib' -task default -os os.osx
...

Normally it should be

05:13:01  Generating make file /Users/jenkins/workspace/Grinder/openjdk-tests/TestConfig/scripts/testKitGen/../../../autoGen.mk
05:13:01  
05:13:01  Generated dependencies.mk
05:13:01  
05:13:01  Generated utils.mk
05:13:01  
05:13:01  Generated count.mk
05:13:01  
05:13:01  TEST AUTO GEN SUCCESSFUL

@karianna
Copy link
Contributor

given #1299 Can this be closed now?

@sophia-guo
Copy link
Contributor

I believe so. If happens again we can reopen or open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants