8275687: runtime/CommandLine/PrintTouchedMethods test shouldn't catch RuntimeException

[fmatte1]

During the review of #5231 (review)
It was suggested by @iklam in the test case Runtime exception is not required for the reason TouchedMethodsDCmd is always enabled as long as the current JVM has INCLUDE_SERVICES is true.

Igor has agreed to capture this in separate RFE (current) to handle this scenario.

This is trivial, please review.

---

Progress

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

Issue

• JDK-8275687: runtime/CommandLine/PrintTouchedMethods test shouldn't catch RuntimeException

Reviewers

• Ioi Lam (@iklam - Reviewer)
• Christian Hagedorn (@chhagedorn - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 6536

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

Using diff file

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

[bridgekeeper]

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

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

• hotspot-runtime

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 (64267837)

[iklam]

LGTM and I agree this is trivial

[openjdk]

@fmatte1 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:

8275687: runtime/CommandLine/PrintTouchedMethods test shouldn't catch RuntimeException

Reviewed-by: iklam, chagedorn

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

• 21e302a: 8270435: UT: MonitorUsedDeflationThresholdTest failed: did not find too_many string in output
• a81e4fc: 8258117: jar tool sets the time stamp of module-info.class entries to the current time
• 26472bd: 8277811: ProblemList vmTestbase/nsk/jdi/TypeComponent/isSynthetic/issynthetic001/TestDescription.java
• b5841ba: 8277806: 4 tools/jar failures per platform after JDK-8272728
• e785f69: 8276124: Provide snippet support for properties files
• 96fe1d0: 8264605: vmTestbase/nsk/jvmti/SuspendThread/suspendthrd003/TestDescription.java failed with "agent_tools.cpp, 471: (foundThread = (jthread) jni_env->NewGlobalRef(foundThread)) != NULL"
• 077b2de: 8274161: Cleanup redundant casts in jdk.compiler
• 951247c: 8235876: Misleading warning message in java source-file mode
• 663e33d: 8272728: javac ignores any -J option in @argfiles silently
• 0384739: 8276665: ObjectInputStream.GetField.get(name, object) should throw ClassNotFoundException

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. Possible candidates are the reviewers of this PR (@iklam, @chhagedorn) 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).

[fmatte1]

LGTM and I agree this is trivial

Thanks, for the review.

[fmatte1]

/integrate

[openjdk]

@fmatte1
Your change (at version 6426783) is now ready to be sponsored by a Committer.

[chhagedorn]

/sponsor

[openjdk]

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

• 21e302a: 8270435: UT: MonitorUsedDeflationThresholdTest failed: did not find too_many string in output
• a81e4fc: 8258117: jar tool sets the time stamp of module-info.class entries to the current time
• 26472bd: 8277811: ProblemList vmTestbase/nsk/jdi/TypeComponent/isSynthetic/issynthetic001/TestDescription.java
• b5841ba: 8277806: 4 tools/jar failures per platform after JDK-8272728
• e785f69: 8276124: Provide snippet support for properties files
• 96fe1d0: 8264605: vmTestbase/nsk/jvmti/SuspendThread/suspendthrd003/TestDescription.java failed with "agent_tools.cpp, 471: (foundThread = (jthread) jni_env->NewGlobalRef(foundThread)) != NULL"
• 077b2de: 8274161: Cleanup redundant casts in jdk.compiler
• 951247c: 8235876: Misleading warning message in java source-file mode
• 663e33d: 8272728: javac ignores any -J option in @argfiles silently
• 0384739: 8276665: ObjectInputStream.GetField.get(name, object) should throw ClassNotFoundException

Your commit was automatically rebased without conflicts.

[openjdk]

@chhagedorn @fmatte1 Pushed as commit f0136ec.

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