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

Merge master #71

Closed
wants to merge 87 commits into from
Closed

Merge master #71

wants to merge 87 commits into from

Conversation

openjdk-bot
Copy link

@openjdk-bot openjdk-bot commented Nov 12, 2020

Hi all,

this is an automatically generated pull request to notify you that there are 87 commits from the branch masterthat can not be merged into the branch records-2:

The following file contains merge conflicts:

  • test/langtools/tools/javac/records/RecordsBinaryCompatibilityTests.java

All Committers in this project have access to my personal fork and can therefore help resolve these merge conflicts (you may want to coordinate who should do this).
The following paragraphs will give an example on how to solve these merge conflicts and push the resulting merge commit to this pull request.
The below commands should be run in a local clone of your personal fork of the openjdk/amber repository.

# Ensure target branch is up to date
$ git checkout records-2
$ git pull https://github.com/openjdk/amber.git records-2

# Fetch and checkout the branch for this pull request
$ git fetch https://github.com/openjdk-bot/amber.git +74:openjdk-bot-74
$ git checkout openjdk-bot-74

# Merge the target branch
$ git merge records-2

When you have resolved the conflicts resulting from the git merge command above, run the following commands to create a merge commit:

$ git add paths/to/files/with/conflicts
$ git commit -m 'Merge master'

When you have created the merge commit, run the following command to push the merge commit to this pull request:

$ git push https://github.com/openjdk-bot/amber.git openjdk-bot-74:74

Note: if you are using SSH to push commits to GitHub, then change the URL in the above git push command accordingly.

Thanks,
J. Duke


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

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/amber pull/71/head:pull/71
$ git checkout pull/71

Update a local copy of the PR:
$ git checkout pull/71
$ git pull https://git.openjdk.org/amber pull/71/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 71

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/amber/pull/71.diff

plummercj and others added 30 commits November 5, 2020 23:18
…ERRUPT after calling RawMonitorEnter

Reviewed-by: alanb, dholmes, sspitsyn
Reviewed-by: redestad, cjplummer, dholmes, stuefe
…escription.java timed out

Reviewed-by: sspitsyn, cjplummer
Reviewed-by: coleenp, gziemski, dholmes
Reviewed-by: azeemj, kizune, prr
Daniel D. Daugherty and others added 22 commits November 11, 2020 16:20
Co-authored-by: Erik Österlund <eosterlund@openjdk.org>
Reviewed-by: eosterlund, rehn, coleenp
8248188: Add IntrinsicCandidate and API for Base64 decoding, add Power64LE intrinsic implementation.

This patch set encompasses the following commits:

Adds a new intrinsic candidate to the java.lang.Base64 class - decodeBlock(), and provides a flexible API for the intrinsic. The API is similar to the existing encodeBlock intrinsic.

Adds the code in HotSpot to check and martial the new intrinsic's arguments to the arch-specific intrinsic implementation.

Adds a Power64LE-specific implementation of the decodeBlock intrinsic.

Adds a JMH microbenchmark for both Base64 encoding and encoding.

Enhances the JTReg hotspot intrinsic "TestBase64.java" regression test to more fully test both decoding and encoding.

Reviewed-by: rriggs, mdoerr, kvn
…ces functionality

Reviewed-by: ayang, iignatyev, iklam
…of trip-counted integer loops

Reviewed-by: chagedorn, thartmann
Reviewed-by: thartmann, chagedorn
Reviewed-by: thartmann, chagedorn
…n Shenandoah root verifier

Reviewed-by: rkennke, shade
@bridgekeeper
Copy link

bridgekeeper bot commented Nov 12, 2020

👋 Welcome back duke! A progress list of the required criteria for merging this PR into records-2 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 added merge-conflict The pull request has a merge conflict with the target branch rfr Ready for review labels Nov 12, 2020
@mlbridge
Copy link

mlbridge bot commented Nov 12, 2020

Webrevs

@bridgekeeper
Copy link

bridgekeeper bot commented Dec 6, 2022

@openjdk-bot 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 Jan 3, 2023

@openjdk-bot 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 Jan 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-auto-merge merge-conflict The pull request has a merge conflict with the target branch rfr Ready for review
Development

Successfully merging this pull request may close these issues.