8230865: [TESTBUG] jdk/jfr/event/io/EvilInstrument.java fails at-run shell MakeJAR.sh target

[zhengyu123]

I would like to backport this patch to fix test failure, introduced by JDK-8223396.

This is a clean backport on top of JDK-8223396 backport.

Test:

• jdk_jfr

---

Progress

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

Issue

• JDK-8230865: [TESTBUG] jdk/jfr/event/io/EvilInstrument.java fails at-run shell MakeJAR.sh target

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 903

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

Using diff file

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

[bridgekeeper]

👋 Welcome back zgu! A progress list of the required criteria for merging this PR into pr/901 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.

[mlbridge]

Webrevs

• 03: Full - Incremental (14e52a35)
• 02: Full - Incremental (cfbb409d)
• 01: Full - Incremental (7a2871ae)
• 00: Full (7a2871ae)

[zhengyu123]

/integrate

[openjdk]

@zhengyu123 This pull request has not yet been marked as ready for integration.

[openjdk-notifier]

The dependent pull request has now been integrated, and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:

git checkout backport-8223396-jfr-test
git fetch https://git.openjdk.java.net/jdk11u-dev master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

[jerboaa]

@zhengyu123 Please follow the steps in comment #903 (comment) so as to make this a clean backport again. Then integration should work.

[openjdk]

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

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

8230865: [TESTBUG] jdk/jfr/event/io/EvilInstrument.java fails at-run shell MakeJAR.sh target

Prebuilding the test class before adding it into a jar file

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:

• 8f3308a: 8217473: SA: Tests using ClhsdbLauncher fail on SAP docker containers
• ca21a70: 8215544: SA: Modify ClhsdbLauncher to add sudo privileges to enable MacOS tests on Mach5

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.

[zhengyu123]

/integrate

[openjdk]

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

• 8f3308a: 8217473: SA: Tests using ClhsdbLauncher fail on SAP docker containers
• ca21a70: 8215544: SA: Modify ClhsdbLauncher to add sudo privileges to enable MacOS tests on Mach5

Your commit was automatically rebased without conflicts.

[openjdk]

@zhengyu123 Pushed as commit 23af0b1.

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