-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
More than half of jdk_jdi tests failed with Dragonwell jdk on packet boxes #1691
Comments
So I think this needs to get transferred to openjdk-infrastructure repo, do you agree @sxa ? |
@sophia-guo - I am going to start closing issues that only contain stale Jenkins links... (since we only keep a small number of builds in history, they disappear before anyone can look at the issue). For now I will grab some more information out of TRSS using its "create new issue" output, so this issue has enough info to give a trail to follow... [2020-09-15T18:02:29.682Z] STDERR: Test Info Build Info Java Version This test has been failed 8 times since Sep 08 2020, 01:29 pm The test failed on machine test-scaleway-ubuntu1604-x64-1 1 times |
Seems reasonable for now - although it's rather odd if it's only an issue for Dragonwell... |
@sophia-guo @smlambert The title of this mentions packet boxes but I don't see any packet ones in the screenshot you've given. Did you mean scaleway? |
Replicated a potential issue outside jenkins and the test harness on the Scaleway machine:
The hostname that the machine has resolves to a There's definitely a difference on Dragonwell in the JDI test - links running on the Scaleway machine for each variant:
|
Doesn't look to be Dragonwell specific - likely HotSpot generally |
HotSpot run after changing |
Killed and restarting as job 600 due to a lot of leftover processes from previous
|
Hmmm possibly different error now from run 600 - none of the output below occurred on the last passing run (job 597 at the time of writing):
|
Backlog for now as not a Temurin build failure |
More than half of jdk_jdi tests failed with Dragonwell jdk8 on packet boxes. Tests passed on other boxes. Also test build took 4 hours compared 40 mins on other boxes. Test builds with hotspot|openj9 on packet boxes also take three times longer than on other boxes without behaviour difference. That is test results are consistent running on packet or other boxes.
https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk8_dragonwell_sanity.openjdk_x86-64_linux/14/
https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk8_dragonwell_sanity.openjdk_x86-64_linux/12/
https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk8_dragonwell_sanity.openjdk_x86-64_linux/10/
Not sure what's the difference between packet boxes with other except for performance?
The text was updated successfully, but these errors were encountered: