Skip to content
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

8284732: FFI_GO_CLOSURES macro not defined but required for zero build on Mac OS X #1374

Conversation

parttimenerd
Copy link
Contributor

@parttimenerd parttimenerd commented Sep 27, 2022


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8284732: FFI_GO_CLOSURES macro not defined but required for zero build on Mac OS X

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk11u-dev pull/1374/head:pull/1374
$ git checkout pull/1374

Update a local copy of the PR:
$ git checkout pull/1374
$ git pull https://git.openjdk.org/jdk11u-dev pull/1374/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1374

View PR using the GUI difftool:
$ git pr show -t 1374

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk11u-dev/pull/1374.diff

@bridgekeeper
Copy link

bridgekeeper bot commented Sep 27, 2022

👋 Welcome back parttimenerd! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk openjdk bot changed the title Backport cafde7fe0025cb648d27c8070689a073e49eabb0 8284732: FFI_GO_CLOSURES macro not defined but required for zero build on Mac OS X Sep 27, 2022
@openjdk
Copy link

openjdk bot commented Sep 27, 2022

This backport pull request has now been updated with issue from the original commit.

@openjdk
Copy link

openjdk bot commented Sep 27, 2022

@parttimenerd This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8284732: FFI_GO_CLOSURES macro not defined but required for zero build on Mac OS X

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 29 new commits pushed to the master branch:

  • 3b9e482: 8211002: test/jdk/java/lang/Math/PowTests.java skips testing for non-corner-case values
  • b6bf677: 8269873: serviceability/sa/Clhsdb tests are using a C2 specific VMStruct field
  • a84c773: 8263326: Remove ReceiverTypeData check from serviceability/sa/TestPrintMdo.java
  • f7e6d0d: 8198343: Test java/awt/print/PrinterJob/TestPgfmtSetMPA.java may fail w/o printer
  • c9d5eb3: 8253877: gc/g1/TestGCLogMessages.java fails - missing "Evacuation failure" message
  • 4b2941d: 8194126: Regression automated Test '/open/test/jdk/javax/swing/JColorChooser/Test7194184.java' fails
  • a48bd87: 8249694: java/lang/StringBuffer/HugeCapacity.java and j/l/StringBuilder/HugeCapacity.java tests shouldn't be @Ignore-d
  • 3ce188b: 8243565: some gc tests use 'test.java.opts' and not 'test.vm.opts'
  • 9c29d00: 8243568: serviceability/logging/TestLogRotation.java uses 'test.java.opts' and not 'test.vm.opts'
  • 3fbcd78: 8215571: jdb does not include jdk.* in the default class filter
  • ... and 19 more: https://git.openjdk.org/jdk11u-dev/compare/6e53ef274a4d7ac058aebba9c1c13b5c297f650a...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot added ready Pull request is ready to be integrated rfr Pull request is ready for review labels Sep 27, 2022
@mlbridge
Copy link

mlbridge bot commented Sep 27, 2022

Webrevs

@parttimenerd
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Oct 10, 2022
@openjdk
Copy link

openjdk bot commented Oct 10, 2022

@parttimenerd
Your change (at version 916b578) is now ready to be sponsored by a Committer.

@GoeLin
Copy link
Member

GoeLin commented Oct 11, 2022

/sponsor

@openjdk
Copy link

openjdk bot commented Oct 11, 2022

Going to push as commit 01d99fa.
Since your change was applied there have been 48 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Oct 11, 2022
@openjdk openjdk bot closed this Oct 11, 2022
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Oct 11, 2022
@openjdk
Copy link

openjdk bot commented Oct 11, 2022

@GoeLin @parttimenerd Pushed as commit 01d99fa.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport clean integrated Pull request has been integrated
2 participants