8210168: JCK test .vm.classfmt.ins.code__002.code__00201m1.code__00201m1 hangs with -noverify

[luchenlin]

I backport this for parity with 11.0.22-oracle.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8210168 needs maintainer approval

Issue

• JDK-8210168: JCK test .vm.classfmt.ins.code__002.code__00201m1.code__00201m1 hangs with -noverify (Bug - P4 - Approved)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 2172

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

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

⚠️ @luchenlin This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[mlbridge]

Webrevs

• 00: Full (2ed15f4b)

[GoeLin]

/approve yes

[openjdk]

@GoeLin
8210168: The approval request has been approved.

[openjdk]

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

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

8210168: JCK test .vm.classfmt.ins.code__002.code__00201m1.code__00201m1 hangs with -noverify

Check for 'bc_length > 0' to handle lengths of -1.

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:

• c4faab6: 8308592: Framework for CA interoperability testing
• df5ff37: 8315683: Parallelize java/util/concurrent/tck/JSR166TestCase.java

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

[luchenlin]

/integrate

[openjdk]

@luchenlin
Your change (at version 2ed15f4) is now ready to be sponsored by a Committer.

[GoeLin]

/sponsor

[openjdk]

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

• c4faab6: 8308592: Framework for CA interoperability testing
• df5ff37: 8315683: Parallelize java/util/concurrent/tck/JSR166TestCase.java

Your commit was automatically rebased without conflicts.

[openjdk]

@GoeLin @luchenlin Pushed as commit b017f76.

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