-
Notifications
You must be signed in to change notification settings - Fork 128
8325194: GHA: Add macOS M1 testing #238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
👋 Welcome back gdams! A progress list of the required criteria for merging this PR into |
This backport pull request has now been updated with issue from the original commit. |
@shipilev still seeing the same error:
I'm slightly confused but I'll do some investigation |
Webrevs
|
We really need to figure out what is missing in JDK repos for this, instead of diverging. We are waiting for https://bugs.openjdk.org/browse/JDK-8324723 to land first to get the msys2 update... |
You should inline the backport of https://bugs.openjdk.org/browse/JDK-8325444 into this. And wait for https://bugs.openjdk.org/browse/JDK-8324723 of course. |
...and by "inline", I think it would be better to revert this PR to original state, add another commit carrying https://bugs.openjdk.org/browse/JDK-8325444, and say |
/issue add JDK-8325444 |
@gdams Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
@gdams |
The test failures will be fixed by merging #254 |
/approval request backport applies cleanly (except for obvious boot JDK URL changes), affects CI only |
I've added the second backport. As for waiting for JDK-8324723, I don't think this is necessary anymore as the build/test is passing in it's current state. CC @shipilev? |
Yes, I don't think it needs to wait for JDK-8324723. |
/approve yes |
@jerboaa |
@gdams This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 3 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
/integrate |
Going to push as commit b9cf41d.
Your commit was automatically rebased without conflicts. |
Now that macOS M1 executors are available in GitHub actions it makes sense to move the build to run on M1 (rather than cross-compiled) and also enable testing on the platform.
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/238/head:pull/238
$ git checkout pull/238
Update a local copy of the PR:
$ git checkout pull/238
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/238/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 238
View PR using the GUI difftool:
$ git pr show -t 238
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/238.diff
Webrev
Link to Webrev Comment