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

8286444: javac errors after JDK-8251329 are not helpful enough to find root cause #1117

Closed

Conversation

RealCLanger
Copy link
Contributor

@RealCLanger RealCLanger commented May 30, 2022

Backport of JDK-8286444. Change did not apply cleanly but only copyright header needed resolving.


Progress

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

Issue

  • JDK-8286444: javac errors after JDK-8251329 are not helpful enough to find root cause

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1117

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

Using diff file

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

@bridgekeeper
Copy link

bridgekeeper bot commented May 30, 2022

👋 Welcome back clanger! 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 29c4b8e80d1860249a79cfd1941354150468fc5b 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause May 30, 2022
@openjdk
Copy link

openjdk bot commented May 30, 2022

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

@openjdk openjdk bot added the backport label May 30, 2022
@RealCLanger
Copy link
Contributor Author

/clean

@openjdk openjdk bot added rfr Pull request is ready for review clean labels May 30, 2022
@openjdk
Copy link

openjdk bot commented May 30, 2022

@RealCLanger This backport pull request is now marked as clean

@openjdk
Copy link

openjdk bot commented May 30, 2022

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

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

8286444: javac errors after JDK-8251329 are not helpful enough to find root cause

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 the ready Pull request is ready to be integrated label May 30, 2022
@mlbridge
Copy link

mlbridge bot commented May 30, 2022

Webrevs

@RealCLanger
Copy link
Contributor Author

Closing in favor of openjdk/jdk11u#37

@RealCLanger RealCLanger closed this Jun 1, 2022
@RealCLanger RealCLanger deleted the RealCLanger-backport-29c4b8e8 branch June 1, 2022 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport clean ready Pull request is ready to be integrated rfr Pull request is ready for review
1 participant