8276623: JDK-8275650 accidentally pushed "out" file

[shipilev]

See the commit: 32895ac

I think this is a trivial fix to remove the accidental addition. I only found this because my local filesystem also has "out" file, and git complained about that pull is about to overwrite it.

---

Progress

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

Issue

• JDK-8276623: JDK-8275650 accidentally pushed "out" file

Reviewers

• Thomas Schatzl (@tschatzl - Reviewer)
• David Holmes (@dholmes-ora - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 6248

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

Using diff file

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

[bridgekeeper]

👋 Welcome back shade! 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]

@shipilev The following label will be automatically applied to this pull request:

• jdk

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (c92cfea3)

[tschatzl]

Lgtm and trivial.

[openjdk]

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

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

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

8276623: JDK-8275650 accidentally pushed "out" file

Reviewed-by: tschatzl, dholmes

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 1 new commit pushed to the master branch:

• a1f4c42: 8276227: ciReplay: SIGSEGV if classfile for replay compilation is not present after JDK-8275868

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.

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

[dholmes-ora]

Thanks for fixing this Aleksey. The fact it was considered a binary file made it easy to overlook in the PR.

Yes this is a trivial fix.

David

[shipilev]

Thanks for quick reviews!

/integrate

[openjdk]

Going to push as commit c62b347.
Since your change was applied there has been 1 commit pushed to the master branch:

• a1f4c42: 8276227: ciReplay: SIGSEGV if classfile for replay compilation is not present after JDK-8275868

Your commit was automatically rebased without conflicts.

[openjdk]

@shipilev Pushed as commit c62b347.

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