8287902: UnreadableRB case in MissingResourceCauseTest is not working reliably on Windows

[gdams]

This pull request contains a backport of JDK-8287902, commit 975316e3 from the openjdk/jdk repository.

The commit being backported was authored by Magnus Ihse Bursie on 10 Jun 2022 and was reviewed by Naoto Sato.

It fixes an issue that shows up in the new style GHA workflow.

---

Progress

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

Issue

• JDK-8287902: UnreadableRB case in MissingResourceCauseTest is not working reliably on Windows

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk11u-dev pull/1542/head:pull/1542
$ git checkout pull/1542

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1542

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

Using diff file

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

[bridgekeeper]

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

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

[openjdk]

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

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

8287902: UnreadableRB case in MissingResourceCauseTest is not working reliably on Windows

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

• 7340e1b: 8287425: Remove unnecessary register push for MacroAssembler::check_klass_subtype_slow_path
• 7964440: 8286624: Regression Test CoordinateTruncationBug.java fails on OL8.3

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.

➡️ 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).

[mlbridge]

Webrevs

• 00: Full (37e76bcf)

[gdams]

/integrate

[openjdk]

@gdams
Your change (at version 37e76bc) is now ready to be sponsored by a Committer.

[gdams]

/sponsor

[RealCLanger]

@gdams Weird that you still need a sponsor. Maybe the Skara bots are checking the JDK repository for committer status (which would be wrong...)

/sponsor

[openjdk]

@gdams Only Committers are allowed to sponsor changes.

[openjdk]

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

• 7340e1b: 8287425: Remove unnecessary register push for MacroAssembler::check_klass_subtype_slow_path
• 7964440: 8286624: Regression Test CoordinateTruncationBug.java fails on OL8.3

Your commit was automatically rebased without conflicts.

[openjdk]

@RealCLanger @gdams Pushed as commit f27d48e.

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