Stewart X Addison
Stewart X Addison
Link to issue: https://www.eclipse.org/forums/index.php/t/1109633/
@knstnce Did you try the 17.0.2 aarch64 binary to see if it has the same problem? The UnsatisfiedLinkError could be from an intel/aarch64 mismatch. And was the Liberica JRE that...
See also this request in the build repo: https://github.com/adoptium/temurin-build/issues/1275
FYI @andrew-m-leonard
@johnoliver Can you clarify what was done to fix this? We should have this documented as part of https://github.com/adoptium/temurin-build/wiki/Setting-up-new-build-jobs,-mirrors,...-when-a-new-openjdk-version-is-branched-from-jdk(head)
Yeah the reason we've enabled regular nightlies is because of the lack of `jdk-21.0.2+` tags (which would be our preferred mechanism of producing new builds) but something (probably the ordering)...
Interesting ... Thanks for the analysis @johnoliver ... In which case the API is doing what I'd expect, but the obvious question is why [the latest builds](https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk21u/job/jdk21u-linux-aarch64-temurin/76/consoleFull) are still identifying...
Yep aware of all that - but we really need a solution to let people get the latest nightlies. Perhaps we need to override it to 21.0.2 or something else...
> Oracle (ie.jdk-21.0.2+1/2/3/4) jdk-21.0.2+0? Gut feel is that it's not ideal to label these nightlies 21.0.1 when they are effectively early builds of 21.0.2. > Can't we just wait 2...
> remember answering the question "can we delete these", and saying yes, but I had assumed the deletion would happen in the Jenkins GUI Ah gotcha - having read this...