On Mon, 23 Jun 2025 08:09:14 GMT, Aleksey Shipilev wrote:
>> See the bug for extended details about this little mess.
>
> Aleksey Shipilev has updated the pull request with a new target base due to a
> merge or a rebase. The pull request now contains one commit:
>
> Try 14.44
2x GHA run is c
On Mon, 23 Jun 2025 08:09:14 GMT, Aleksey Shipilev wrote:
>> See the bug for extended details about this little mess.
>
> Aleksey Shipilev has updated the pull request with a new target base due to a
> merge or a rebase. The pull request now contains one commit:
>
> Try 14.44
Marked as revie
On Fri, 20 Jun 2025 08:36:30 GMT, Aleksey Shipilev wrote:
> See the bug for extended details about this little mess.
Looks like `20250617.1.0` runner image have been deployed. We can go in with
this PR now. Please review.
-
PR Comment: https://git.openjdk.org/jdk/pull/25912#issuec
On Mon, 23 Jun 2025 08:09:14 GMT, Aleksey Shipilev wrote:
>> See the bug for extended details about this little mess.
>
> Aleksey Shipilev has updated the pull request with a new target base due to a
> merge or a rebase. The pull request now contains one commit:
>
> Try 14.44
As you say, it
> See the bug for extended details about this little mess.
Aleksey Shipilev has updated the pull request with a new target base due to a
merge or a rebase. The pull request now contains one commit:
Try 14.44
-
Changes: https://git.openjdk.org/jdk/pull/25912/files
Webrev: https:
On Fri, 20 Jun 2025 11:16:52 GMT, Antonio Vieiro wrote:
>> See the bug for extended details about this little mess.
>
> Looks like [it cannot find a C
> compiler](https://github.com/openjdk/jdk/blob/8f121a173ca2534c706682f6c68fbbb0b94ec057/make/autoconf/toolchain.m4#L469)
> on `windows-x64`...
On Fri, 20 Jun 2025 08:36:30 GMT, Aleksey Shipilev wrote:
> See the bug for extended details about this little mess.
Looks like [it cannot find a C
compiler](https://github.com/openjdk/jdk/blob/8f121a173ca2534c706682f6c68fbbb0b94ec057/make/autoconf/toolchain.m4#L469)
on `windows-x64`...
[.
On Fri, 20 Jun 2025 08:36:30 GMT, Aleksey Shipilev 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 im
