Making jdk for jtreg build explicit #1019
Conversation
and so imune against change of system jdk on underlying system/image
Thank you for creating a pull request!Please check out the information below if you have not made a pull request here before (or if you need a reminder how things work). Code Quality and Contributing GuidelinesIf you have not done so already, please familiarise yourself with our Contributing Guidelines and Code Of Conduct, even if you have contributed before. TestsGithub actions will run a set of jobs against your PR that will lint and unit test your changes. Keep an eye out for the results from these on the latest commit you submitted. For more information, please see our testing documentation. In order to run the advanced pipeline tests (executing a set of mock pipelines), it requires an admin to post |
|
This should fix the currently broken codetools - eg https://ci.adoptium.net/view/Dependencies/job/dependency_pipeline/1155/ It seesm that system jdk changed on that underlying system, and so old jtregs, were pulling to fresh jdk. I'm a bit concerned about I will add a commits on this topic, but first let ssee if it fixes it. |
Also put the "expected" java into the start, as otherwise the system JDK would be always before the "expected" jdk. I think the meddling wiht PATH is actually useless, but I do not see to the bottom of this script. Am in temptation to remove that at all. But that can bite
|
cool! ty! |
and so imune against change of system jdk on underlying system/image