Skip to content
This repository has been archived by the owner. It is now read-only.

Merge jdk:master #131

wants to merge 34 commits into from

Merge jdk:master #131

wants to merge 34 commits into from


Copy link

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

Hi all,

this is an automatically generated pull request to notify you that there are 33 commits from the branch jdk:masterthat can not be merged into the branch master:

The following file contains merge conflicts:

  • .jcheck/conf

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/lanai repository.

# Ensure target branch is up to date
$ git checkout master
$ git pull master

# Fetch and checkout the branch for this pull request
$ git fetch +6:openjdk-bot-6
$ git checkout openjdk-bot-6

# Merge the target branch
$ git merge master

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 jdk:master'

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

$ git push openjdk-bot-6:6

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

J. Duke


  • Change must not contain extraneous whitespace


Linux aarch64 Linux arm Linux ppc64le Linux s390x Linux x64 Linux x86 Windows x64 macOS x64
Build (1/1 running) (1/1 running) (1/1 running) (1/1 running) ✔️ (6/6 passed) ✔️ (2/2 passed) (2/2 running) ✔️ (2/2 passed)
Test (tier1) (7/9 running) (9/9 running) (1/9 failed)

Failed test task


$ git fetch pull/131/head:pull/131
$ git checkout pull/131

Alexander Zuev and others added 30 commits Nov 20, 2020

Reviewed-by: stuefe, coleenp, dcubed
… fails

Reviewed-by: cjplummer, sspitsyn
…to access variable sized PtrQueue::_index

Reviewed-by: shade
…useless_nodes missed this node")

Check for nodes missed by remove_useless_nodes() only if PhaseRemoveUseless has
actually been run. This makes it possible to use -XX:-UseLoopSafepoints without
crashing trivially, although implicit assumptions in other parts of C2 about the
existence of loop safepoints might lead to more subtle failures for more complex

Reviewed-by: neliasso, thartmann, kvn
Reviewed-by: ayang, eosterlund
Reviewed-by: kvn, shade, thartmann
8231547: Serializable class doc should link to serialization specification

Reviewed-by: rriggs, iris, chegar
…rrent code root evacuator

Reviewed-by: rkennke
…e initializing cgroupv1 subsystem

Reviewed-by: shade, sgehwolf, bobv
Reviewed-by: dfuchs, lancea, bpb
@openjdk openjdk bot added the failed-auto-merge label Nov 21, 2020
Copy link

@bridgekeeper bridgekeeper bot commented Nov 21, 2020

👋 Welcome back duke! 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 added merge-conflict rfr labels Nov 21, 2020
Copy link

@mlbridge mlbridge bot commented Nov 21, 2020

Copy link

@openjdk openjdk bot commented Nov 21, 2020

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

ℹ️ This project also has non-automated pre-integration requirements. Please see the file for details.

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

Merge jdk:master

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.

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 and removed merge-conflict labels Nov 21, 2020
Copy link

@kevinrushforth kevinrushforth commented Nov 21, 2020


Copy link

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


Copy link

@openjdk openjdk bot commented Nov 21, 2020

@kevinrushforth Only the author (@openjdk-bot) is allowed to issue the integrate command.

@openjdk openjdk bot added the sponsor label Nov 21, 2020
Copy link

@openjdk openjdk bot commented Nov 21, 2020

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

Copy link

@kevinrushforth kevinrushforth commented Nov 21, 2020


@openjdk openjdk bot closed this Nov 21, 2020
@openjdk openjdk bot added integrated and removed sponsor ready rfr labels Nov 21, 2020
Copy link

@openjdk openjdk bot commented Nov 21, 2020

@kevinrushforth @openjdk-bot Pushed as commit 155894a.

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

@kevinrushforth kevinrushforth deleted the 6 branch Nov 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
failed-auto-merge integrated