adoptium / adoptium/infrastructure
More than half of jdk_jdi tests failed with Dragonwell jdk on packet boxes
- Dominant language
- Python
- Stars
- 96
- Forks
- 106
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
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?
Contributor guide
Research direction
Start by reviewing the linked Test_openjdk8_dragonwell_sanity.openjdk_x86-64_linux Jenkins runs and the jdk_jdi results, then compare them with hotspot and openj9 runs on packet and other boxes. Done means identifying the packet-box difference that causes the failures and threefold-or-worse runtime increase, with comparable test results and build duration restored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, infrastructure, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100