-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
8276854: Windows GHA builds fail due to broken Cygwin #6319
Conversation
👋 Welcome back asarkar! A progress list of the required criteria for merging this PR into |
@AnirvanSarkar The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. Thanks for doing this fix. And thanks to @shipilev for chasing this down.
@AnirvanSarkar 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 6 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 As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@RealCLanger) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@AnirvanSarkar |
/sponsor |
Going to push as commit 403f318.
Your commit was automatically rebased without conflicts. |
@RealCLanger @AnirvanSarkar Pushed as commit 403f318. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The patch looks okay. But what just happened here process-wise? Please do not take the issue out of assignee's hands without asking first, and definitely do NOT push the fix until the original assignee at least performs some sort of handover. Especially don't do that in the span of less than 24 hours, where the assignee might just be asleep. I also suspect the build infra changes require more reviews, anyway. Don't rush it, folks! |
Yes, that was odd. Please don't reassign JBS issues unless you either talk with the assignee or it has been clearly abandoned. |
It is my mistake. Sorry for rushing and breaking the etiquette. |
Good, thanks. No harm done in this particular case, as the patch is definitely sensible. I'll handle the backports... |
Mailing list message from Magnus Ihse Bursie on build-dev: https://openjdk.java.net/census#build On 2021-11-10 08:48, Aleksey Shipilev wrote:
I would like to add to Aleksey's comment that the ideal is that you get /Magnus |
That was also my mistake (probably even more than Anirvan's) since I sponsored this too early and I should have taken care for all the points mentioned above. Sorry folks! |
Use version
3.2.0
ofcygwin
instead of latest version3.3.2
on GitHub Actions.make
SEGVs on the latest version.Version number format obtained from https://cygwin.com/packages/summary/cygwin.html
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6319/head:pull/6319
$ git checkout pull/6319
Update a local copy of the PR:
$ git checkout pull/6319
$ git pull https://git.openjdk.java.net/jdk pull/6319/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6319
View PR using the GUI difftool:
$ git pr show -t 6319
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6319.diff