jcstress dependencies are unclear
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
The getDepenencies is pulling jcstress-tests-all-20240222.jar'
https://github.com/adoptium/TKG/blob/master/scripts/getDependencies.pl#L182
in addition, it is pulling it from personal server
however, the https://github.com/adoptium/aqa-tests/blob/master/system/jcstress/playlist.xml
is using jcstress-tests-all-20220908.jar
The 20220908 is nowhere to be obtained, so unless it is manually in `$(LIB) ` it fails.
I would like to do following changes:
* improve https://ci.adoptium.net/view/Dependencies/job/dependency_pipeline/lastSuccessfulBuild/artifact/jcstress/ so it builds jcstress-tests-all-20220908.jar and jcstress-tests-all-20240222.jar and tip
* change getDependencies.pl so it is pulling three jcstress jars from https://ci.adoptium.net/view/Dependencies/job/dependency_pipeline/lastSuccessfulBuild/ instead of https://builds.shipilev.net/jcstress/
* improve https://github.com/adoptium/TKG/blob/master/scripts/getDependencies.xml so it have target, which will prepare jcstress.jar per JDK version, as jtregs are doing it.
* improve https://github.com/adoptium/aqa-tests/blob/master/system/jcstress/playlist.xml so it is using jcstress jar per jdk version
* I would like to use 20240222 everywhere where possible. Use 20220908 as fallback, and maybe use tip for future jdk
* if possible, I would like to revisit targets in https://github.com/adoptium/aqa-tests/blob/master/system/jcstress/playlist.xml so they enumeare all possible targets (based on version of jcstress?). But tbh, I had not yet properly looked into it.
WDYT?
Contributor guide
Research direction
Start by comparing scripts/getDependencies.pl, scripts/getDependencies.xml, and system/jcstress/playlist.xml with the dependency_pipeline jcstress artifact linked in the issue. Define the supported JDK and jcstress-version mapping, then verify that the requested jars are built, retrieved, and selected consistently by the playlist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100