Mode definition inconsistencies in modes.xml
- Dominant language
- Java
- Stars
- 22
- Forks
- 114
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 8
Description
Some modes have inconsistent definitions of `clArg` and `envVar`, as shown below:
Mode 122 and 622: The `optlevel` is `warm` in `clArg`, while `envVar` specifies `hot`:
- https://github.com/adoptium/TKG/blob/9db2f4162fc930a8a6980c685c5a7466cda63ee9/resources/modes.xml#L506-L507
- https://github.com/adoptium/TKG/blob/9db2f4162fc930a8a6980c685c5a7466cda63ee9/resources/modes.xml#L4038-L4039
Mode 208: Only `envVar` has `-Xgcthreads${MAX_GC_THREADS}`:
- https://github.com/adoptium/TKG/blob/9db2f4162fc930a8a6980c685c5a7466cda63ee9/resources/modes.xml#L2144-L2145
Contributor guide
Research direction
Start in resources/modes.xml at the referenced definitions for modes 122, 622, and 208. Compare each mode's clArg and envVar values, determine the consistent definitions intended by the surrounding entries, and validate that the affected mode configurations agree when the work is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100