Refactor ProblemList_openjdk**-openj9.txt to openj9 | ibm folder.
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
Vendor specific ProblemLists (excludes/vendors/vendor/ProblemList_openjdk*.txt) is used for handling vendor specific features . Common temporary problemlists stays in openjdk/excludes/ProblemList_openjdk*.txt.
Currently openj9|IBM problemlists is an exception, which has a different name for problemlist. Most of the exclusions in problemlist is duplicated in openj9 problemlist. And when re-enable both files need to be updated.
Suggest to refactor those files. Move openj9 problemlist to openj9|ibm as a vendor folder. Renaming the "-openj9" problemlist as normal ones. Removing all duplicate exclusions in openj9 problemlist.
This can eliminate the redundancy, ease the maintenance, improve the consistency and make openj9 problemlist simple and clear to its own issues.
Contributor guide
Research direction
Start by reading the vendor-specific lists under excludes/vendors/vendor/ProblemList_openjdk*.txt and the common lists under openjdk/excludes/ProblemList_openjdk*.txt, then locate the current OpenJ9/IBM list described in the issue. Compare the exclusions, move and rename the OpenJ9 list into the vendor folder, and remove duplicates; done means the vendor layout is consistent and redundant exclusions are gone.
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