-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
Comments
The tests execute OK when I reran them as a Test_grinder job: https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/1925/console |
@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 |
The next jdk11 build is fine https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_extended.system_x86-64_mac/26/ |
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. |
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 |
Looks like build workspace is not clean https://ci.adoptopenjdk.net/job/Test_openjdk11_j9_extended.system_x86-64_mac/25/console
In a clean build there shouldn't be any files. My guess is because of this TEST AUTO GEN wasn't SUCCESSFUL.
Normally it should be
|
given #1299 Can this be closed now? |
I believe so. If happens again we can reopen or open a new one. |
All the extended system tests run by the build pipeline for the rerelease of jdk11u on MacOS failed with these messages:
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
The text was updated successfully, but these errors were encountered: