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

8280786: Build failure on Solaris after 8262392 #27

Closed
wants to merge 1 commit into from

Conversation

GoeLin
Copy link
Member

@GoeLin GoeLin commented Feb 7, 2022

See See http://mail.openjdk.java.net/pipermail/jdk-updates-dev/2022-February/011862.html


Progress

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

Issue

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u pull/27/head:pull/27
$ git checkout pull/27

Update a local copy of the PR:
$ git checkout pull/27
$ git pull https://git.openjdk.java.net/jdk11u pull/27/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u/pull/27.diff

@bridgekeeper
Copy link

bridgekeeper bot commented Feb 7, 2022

👋 Welcome back goetz! 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 6837e1484bbeda710cde3763f0b0edb9c02351c2 8280786: Build failure on Solaris after 8262392 Feb 7, 2022
@openjdk
Copy link

openjdk bot commented Feb 7, 2022

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

@openjdk
Copy link

openjdk bot commented Feb 7, 2022

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

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

8280786: Build failure on Solaris after 8262392

Reviewed-by: clanger

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot added ready rfr labels Feb 7, 2022
@mlbridge
Copy link

mlbridge bot commented Feb 7, 2022

Webrevs

@GoeLin
Copy link
Member Author

GoeLin commented Feb 7, 2022

Pre-submit test failure: gc/metaspace/TestMetaspacePerfCounters.java#id1, this test keeps failing in the Pre-submit tests; unrelated.

@GoeLin
Copy link
Member Author

GoeLin commented Feb 7, 2022

/integrate

@openjdk
Copy link

openjdk bot commented Feb 7, 2022

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

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated label Feb 7, 2022
@openjdk openjdk bot closed this Feb 7, 2022
@openjdk openjdk bot removed ready rfr labels Feb 7, 2022
@openjdk
Copy link

openjdk bot commented Feb 7, 2022

@GoeLin Pushed as commit b8cdf1a.

💡 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
2 participants