On Wed, 7 Feb 2024 19:30:17 GMT, George Adams wrote:
> > Opened [JDK-8325444](https://bugs.openjdk.org/browse/JDK-8325444) and
> > trying a fix in https://github.com/RealCLanger/jdk/actions/runs/7820130826
>
> I like your approach, it feels more robust
Yeah, but didn't work. Here's a PR with
On Wed, 7 Feb 2024 19:29:02 GMT, Christoph Langer wrote:
> Opened [JDK-8325444](https://bugs.openjdk.org/browse/JDK-8325444) and trying
> a fix in https://github.com/RealCLanger/jdk/actions/runs/7820130826
I like your approach, it feels more robust
-
PR Comment:
On Sat, 3 Feb 2024 21:55:25 GMT, George Adams wrote:
>> Now that macOS M1 executors are [available in GitHub
>> actions](https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source/)
>> it makes sense to move the build to run on M1
On Wed, 7 Feb 2024 19:21:24 GMT, Christoph Langer wrote:
>> Okay, this one regressed GHA for new PRs:
>> https://github.com/stefank/jdk/actions/runs/7817217154/job/21324582843
>>
>>
>> Run # Build JTReg and move files to the proper locations
>> realpath: bootjdk/jdk: No such file or directory
On Wed, 7 Feb 2024 15:59:00 GMT, Aleksey Shipilev wrote:
> Okay, this one regressed GHA for new PRs:
> https://github.com/stefank/jdk/actions/runs/7817217154/job/21324582843
>
> ```
> Run # Build JTReg and move files to the proper locations
> realpath: bootjdk/jdk: No such file or directory
>
On Sat, 3 Feb 2024 21:55:25 GMT, George Adams wrote:
>> Now that macOS M1 executors are [available in GitHub
>> actions](https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source/)
>> it makes sense to move the build to run on M1
On Sat, 3 Feb 2024 21:55:25 GMT, George Adams wrote:
>> Now that macOS M1 executors are [available in GitHub
>> actions](https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source/)
>> it makes sense to move the build to run on M1
On Sat, 3 Feb 2024 21:55:25 GMT, George Adams wrote:
>> Now that macOS M1 executors are [available in GitHub
>> actions](https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source/)
>> it makes sense to move the build to run on M1
> Now that macOS M1 executors are [available in GitHub
> actions](https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source/)
> it makes sense to move the build to run on M1 (rather than cross-compiled)
> and also enable testing on the
