Closed Haroon-Khel closed 3 months ago
Running jdk 11 tests on test-docker-alpine320-x64-1 which is using jdk21 as its default https://ci.adoptium.net/job/Grinder/10571/console
AQA test pipeline for JDK8 11 17 and 21 on all of our x64 Alpine boxes to make sure other JDKs arent affected https://ci.adoptium.net/job/AQA_Test_Pipeline/336/console
Its having trouble building the downstream jobs off my branch, https://ci.adoptium.net/job/Test_openjdk8_hs_special.functional_x86-64_alpine-linux/112/console for example
hudson.plugins.git.GitException: Command "git fetch --tags --force --progress --prune -- origin +refs/heads/alpine.library:refs/remotes/origin/alpine.library" returned status code 128:
stdout:
stderr: fatal: couldn't find remote ref refs/heads/alpine.library
Its using origin
in place of my fork. My fork and branch have been passed to the job in the parameters section
Ill run them as grinders in the meantime, just the extended tests jdk8 https://ci.adoptium.net/job/Grinder/10582/console jdk11 https://ci.adoptium.net/job/Grinder/10583/console jdk17 https://ci.adoptium.net/job/Grinder/10584/console jdk21 https://ci.adoptium.net/job/Grinder/10585/console
And ive changed the default jdk on our x64 alpine boxes back to 21 (ref https://github.com/adoptium/infrastructure/issues/3529#issuecomment-2217595206)
Its using
origin
in place of my fork. My fork and branch have been passed to the job in the parameters section
Interesting - I hit a similar issue recently too - maybe post in #aqa-tests to see if anyone can explain/mitigate it? Can't think why Grinder would be different but I think that's what I experienced too.
Each of the grinders compiled and were built fine, other jdks have not been affected. This pr can be merged
Testing to see if this fixes https://github.com/adoptium/aqa-tests/issues/5425 and https://github.com/adoptium/infrastructure/issues/3529