8042726: [TESTBUG] TEST.groups file was not updated after runtime/6925573/SortMethodsTest.java removal

[benty-amzn]

Backport JDK-8042726 as a follow-up to #351, to resolve a bug in that backport. Change has merge conflicts due to changes in context line, but the change itself is clean as it is a single-line deletion.

---

Progress

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

Issue

• JDK-8042726: [TESTBUG] TEST.groups file was not updated after runtime/6925573/SortMethodsTest.java removal (Bug - P4)

Reviewers

• Severin Gehwolf (@jerboaa - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 355

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back btaylor! 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 and summary from the original commit.

[openjdk]

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

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

8042726: [TESTBUG] TEST.groups file was not updated after runtime/6925573/SortMethodsTest.java removal

Removed runtime/6925573/SortMethodsTest.java from TEST.groups

Reviewed-by: sgehwolf

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. Possible candidates are the reviewers of this PR (@jerboaa) but any other Committer may sponsor as well.

➡️ 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 (4eaea91b)

[jerboaa]

LGTM. I've also approved the bug for 8u.

[benty-amzn]

/integrate

[openjdk]

@benty-amzn
Your change (at version 4eaea91) is now ready to be sponsored by a Committer.

[phohensee]

/sponsor

[openjdk]

Going to push as commit 3232400.

[openjdk]

@phohensee @benty-amzn Pushed as commit 3232400.

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