3rd party libs should be downloaded via getDependency job
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
Some 3rd libs get downloaded at runtime (see the links below).
https://github.com/adoptium/aqa-tests/blob/1898c35e22a6100c7be9d9270cad110bfe9b2d52/perf/dacapo/build.xml#L37
https://github.com/adoptium/aqa-tests/blob/f9c915a44322fab060e3dc13c5db0ce4b5dddc52/perf/renaissance/build.xml#L37
Depending on the network status and 3rd party server availability, we may run into the issue of having Invalid or corrupt jarfile (see runtimes/backlog/issues/872). We should pre-download the 3rd party lib via https://ci.adoptopenjdk.net/job/test.getDependency/
code is in TKG: https://github.com/adoptium/TKG/blob/ae395bd9f8dff8ab73e39608916955147308e1aa/scripts/getDependencies.pl#L62
Contributor guide
Research direction
Start by reading the dependency download sections in perf/dacapo/build.xml and perf/renaissance/build.xml, then inspect scripts/getDependencies.pl and the referenced test.getDependency job. Confirm how each third-party library is obtained and what the generated test inputs expect. Done means the libraries are pre-downloaded through the dependency job rather than fetched at runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, perl
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100