On Fri, 20 Jun 2025 08:36:30 GMT, Aleksey Shipilev <sh...@openjdk.org> wrote:
> See the bug for extended details about this little mess. Great, I can see that new runner image does _not_ like `14.43`. So we are in weird spot at the moment: - Old runner image works with `14.43`, fails with `14.44` - New runner image fails with `14.43`, works with `14.44` - Old -> new runner image is currently deploying. About 1/4 of jobs I have seen still get the old runner image at the moment of writing. Given that new runner image would eventually deploy everywhere, this IMO leaves us with no choice but to do the `14.44` switch now. On the up-side, compared to `14.43`, `14.44` is actually claimed to be available by runner docs. With `14.43`, we are playing with fire anyway. ------------- PR Comment: https://git.openjdk.org/jdk/pull/25912#issuecomment-2990360772
