Skip to content

Conversation

@dongbohe
Copy link
Member

@dongbohe dongbohe commented Mar 21, 2022

Hi,

I would like to backport this as follow up of JDK-8173361, only a different context.

Thanks,
hedongbo


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • 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.org/jdk8u-dev pull/19/head:pull/19
$ git checkout pull/19

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 19

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

Using diff file

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

@bridgekeeper
Copy link

bridgekeeper bot commented Mar 21, 2022

👋 Welcome back dongbohe! A progress list of the required criteria for merging this PR into pr/9 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 c10f731b11f314c97660df08c62f3c3d2f718f54 8235218: Minimal VM is broken after JDK-8173361 Mar 21, 2022
@openjdk
Copy link

openjdk bot commented Mar 21, 2022

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

@openjdk openjdk bot added backport Port of a pull request already in a different code base rfr Pull request is ready for review labels Mar 21, 2022
@mlbridge
Copy link

mlbridge bot commented Mar 21, 2022

Webrevs

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 18, 2022

@dongbohe This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@bridgekeeper
Copy link

bridgekeeper bot commented May 16, 2022

@dongbohe This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the /open pull request command.

@bridgekeeper bridgekeeper bot closed this May 16, 2022
@dongbohe
Copy link
Member Author

/open

@openjdk openjdk bot reopened this May 30, 2022
@openjdk
Copy link

openjdk bot commented May 30, 2022

@dongbohe This pull request is now open

@bridgekeeper
Copy link

bridgekeeper bot commented Jun 27, 2022

@dongbohe This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@gnu-andrew
Copy link
Member

The target of this PR seems wrong. It should be 8u/master not 8u/pr/9. Maybe easier to start fresh?

@openjdk-notifier openjdk-notifier bot changed the base branch from pr/9 to master June 29, 2022 16:38
@openjdk-notifier
Copy link

The dependent pull request has now been integrated, and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:

git checkout 8235218
git fetch https://git.openjdk.org/jdk8u-dev master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

@dongbohe
Copy link
Member Author

According to the description of New Skara feature: dependent pull requests, we need to target to pr/9.

It seems that I need to merge master, I will try.

@dongbohe
Copy link
Member Author

It looks ok.

@dongbohe
Copy link
Member Author

dongbohe commented Jul 5, 2022

@gnu-andrew Hi, Andrew. Could you please take another look?

Copy link
Contributor

@jerboaa jerboaa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks OK.

@openjdk
Copy link

openjdk bot commented Jul 8, 2022

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

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

8235218: Minimal VM is broken after JDK-8173361

Reviewed-by: sgehwolf, andrew

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

  • eeef4de: 8150669: C1 intrinsic for Class.isPrimitive
  • 6e8292f: 8283849: AsyncGetCallTrace may crash JVM on guarantee
  • ce73401: 8136354: [TEST_BUG] Test java/awt/image/RescaleOp/RescaleAlphaTest.java with Bad action for script
  • a3c0ed2: 8087283: Add support for the XML Signature here() function to the JDK XPath implementation

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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. Possible candidates are the reviewers of this PR (@jerboaa, @gnu-andrew) but any other Committer may sponsor as well.

➡️ 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 the ready Pull request is ready to be integrated label Jul 8, 2022
@dongbohe
Copy link
Member Author

dongbohe commented Jul 8, 2022

Got the push approval.
/integrate

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

openjdk bot commented Jul 8, 2022

@dongbohe
Your change (at version cc2d678) is now ready to be sponsored by a Committer.

@gnu-andrew
Copy link
Member

According to the description of New Skara feature: dependent pull requests, we need to target to pr/9.

It seems that I need to merge master, I will try.

Ah ok, that's the first I've heard of that. It seems the mail was only sent to jdk-dev and not the jdk-updates or jdk8u lists.

Copy link
Member

@gnu-andrew gnu-andrew left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Backport itself looks clean.

@gnu-andrew
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Jul 10, 2022

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

  • eeef4de: 8150669: C1 intrinsic for Class.isPrimitive
  • 6e8292f: 8283849: AsyncGetCallTrace may crash JVM on guarantee
  • ce73401: 8136354: [TEST_BUG] Test java/awt/image/RescaleOp/RescaleAlphaTest.java with Bad action for script
  • a3c0ed2: 8087283: Add support for the XML Signature here() function to the JDK XPath implementation

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jul 10, 2022
@openjdk openjdk bot closed this Jul 10, 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 Jul 10, 2022
@openjdk
Copy link

openjdk bot commented Jul 10, 2022

@gnu-andrew @dongbohe Pushed as commit e005185.

💡 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 Port of a pull request already in a different code base integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants