Only run test-result-gathering on specific machines
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
**Summary**
Some test jobs failed as the test gathering process was sent to a machine that could not complete the job. We should have worker labels on nodes that are safe for these jobs.
We should also modify these jobs to ensure they only use those nodes.
**Details**
Text below from:
https://github.com/adoptium/aqa-tests/issues/5444#issuecomment-2233270448
x86-64_windows 21
extended.perf
Failed when collecting artifacts via machine test-sxa-armv7l-ubuntu2004-odroid-2
[2024-07-17T06:00:38.100Z] Running on test-sxa-armv7l-ubuntu2004-odroid-2 in /ssd/jenkins/workspace/Test_openjdk21_hs_sanity.perf_x86-64_windows
...
[2024-07-17T06:04:49.333Z] Exception: hudson.remoting.RequestAbortedException: java.nio.channels.ClosedChannelException
https://ci.adoptium.net/job/Test_openjdk21_hs_sanity.perf_x86-64_windows/159/consoleText
Originally mentioned in July 2024 General Retrospective
https://github.com/adoptium/temurin/issues/50
Contributor guide
Research direction
Start with the linked Jenkins console output for Test_openjdk21_hs_sanity.perf_x86-64_windows and trace how test-result-gathering jobs select worker nodes. Identify the relevant job or node-label configuration, then verify that gathering runs only on safe labeled machines and no longer selects the failing ARM worker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, infrastructure, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100