adoptium / adoptium/aqa-tests

Clean up ProblemList_openjdkXXX-openj9.txt for openj9

Open
#5,860 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
155
Forks
346
Avg merge
2d 9h
Merged PRs (30d)
36

Description

Check the JDK8, 11, 17, 21, 24, and 25 ProblemList_openjdkXXX-openj9.txt files under https://github.com/adoptium/aqa-tests/tree/master/openjdk/excludes. Ideally, they should only contain issues related to [JBS](https://bugs.openjdk.org/), openj9, and runtimes.

- If the subtest is excluded due to `adoptium/infrastructure/issues`, rerun to see if we have the same issue in hyc Jenkins.
- If not, re-include the subtest.
- Otherwise, check if there are any existing [runtimes/infrastructure](https://github.ibm.com/runtimes/infrastructure) issues.
- If not, please open the issue in runtimes/infrastructure and link adoptium/infrastructure/issues
- Otherwise, update the issue URL to runtimes/infrastructure issue
- Repeat for the subtest that is excluded due to `adoptium/aqa-tests/issues`. If a new issue needs to be opened, it should be opened at [runtimes/backlog](https://github.ibm.com/runtimes/backlog/issues)

I suggest starting with [JDK21](https://github.com/adoptium/aqa-tests/blob/master/openjdk/excludes/ProblemList_openjdk21-openj9.txt).

Please ignore the exclude due to Permanent excludes https://github.com/adoptium/aqa-tests/issues/1297

Contributor guide

Open the contributing guide

Research direction

Start with openjdk/excludes/ProblemList_openjdk21-openj9.txt, then review the corresponding JDK8, 11, 17, 24, and 25 files. For entries tied to adoptium/infrastructure/issues or adoptium/aqa-tests/issues, rerun the subtests and check the referenced infrastructure or backlog issues. Done means unrelated exclusions are re-included and remaining entries point to appropriate JBS, OpenJ9, runtime, infrastructure, or backlog issues, excluding permanent excludes.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
testing-qa
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.