Skip to content

Conversation

@alexmenkov
Copy link

@alexmenkov alexmenkov commented May 21, 2025

The change fixes failure of vmTestbase/nsk/jvmti/AttachOnDemand/attach045/TestDescription.java test.
The test was problem-listed in jdk 11 due intermittent timeouts, but in jdk15-16 changes in nsk framework made the test fail 100% (it wasn't noticed as the test was problemlisted)
The problem is attach045 has "target" parameter which contain class name and arguments (all other tests have only class name), and value of the argument is passed in surrounding quotes, so target application fails with ClassNotFoundException.
Now I cannot reproduce original test failure, so removing the test from problemlist


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8357282: Test vmTestbase/nsk/jvmti/AttachOnDemand/attach045/TestDescription.java fails after ClassNotFoundException (Bug - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25366/head:pull/25366
$ git checkout pull/25366

Update a local copy of the PR:
$ git checkout pull/25366
$ git pull https://git.openjdk.org/jdk.git pull/25366/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25366

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25366.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented May 21, 2025

👋 Welcome back amenkov! 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
Copy link

openjdk bot commented May 21, 2025

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

8357282: Test vmTestbase/nsk/jvmti/AttachOnDemand/attach045/TestDescription.java fails after ClassNotFoundException

Reviewed-by: lmesnik, sspitsyn

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 135 new commits pushed to 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.

@openjdk openjdk bot added the rfr Pull request is ready for review label May 21, 2025
@openjdk
Copy link

openjdk bot commented May 21, 2025

@alexmenkov To determine the appropriate audience for reviewing this pull request, one or more labels corresponding to different subsystems will normally be applied automatically. However, no automatic labelling rule matches the changes in this pull request. In order to have an "RFR" email sent to the correct mailing list, you will need to add one or more applicable labels manually using the /label pull request command.

Applicable Labels
  • build
  • client
  • compiler
  • core-libs
  • graal
  • hotspot
  • hotspot-compiler
  • hotspot-gc
  • hotspot-jfr
  • hotspot-runtime
  • i18n
  • ide-support
  • javadoc
  • jdk
  • jmx
  • kulla
  • net
  • nio
  • security
  • serviceability
  • shenandoah

@alexmenkov
Copy link
Author

/label add serviceability

@openjdk openjdk bot added the serviceability serviceability-dev@openjdk.org label May 21, 2025
@openjdk
Copy link

openjdk bot commented May 21, 2025

@alexmenkov
The serviceability label was successfully added.

@mlbridge
Copy link

mlbridge bot commented May 21, 2025

Webrevs

Copy link
Member

@lmesnik lmesnik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I understand, this fix is not related to timeout. So test is going to fail. It might be makes a sense to remove it from problemlist to see how it works. However better to rename PR summary.

}

return options.getProperty(TARGET_APP_PARAM);
String target = options.getProperty(TARGET_APP_PARAM);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is better to remove -classPath from parameters and
use
${test.class.path}
directly in the test.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test is run by nsk.share.aod.AODTestRunner which runs test app specified by "target" argument.
Target apps have no system properties like test.class.path

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for explanation.

@alexmenkov alexmenkov changed the title 8357282: Test vmTestbase/nsk/jvmti/AttachOnDemand/attach045/TestDescription.java times out after ClassNotFoundException 8357282: Test vmTestbase/nsk/jvmti/AttachOnDemand/attach045/TestDescription.java fails after ClassNotFoundException May 22, 2025
@alexmenkov
Copy link
Author

As I understand, this fix is not related to timeout. So test is going to fail. It might be makes a sense to remove it from problemlist to see how it works. However better to rename PR summary.

Oh, right. It's socket timeout, not the test timeout. Renamed JBS issue

@sspitsyn
Copy link
Contributor

Oh, right. It's socket timeout, not the test timeout. Renamed JBS issue

Nit: Would it better to replace: "fails after ClassNotFoundException" => "fails with ClassNotFoundException" ?

@sspitsyn
Copy link
Contributor

sspitsyn commented May 23, 2025

This test was marked in ProblemList with https://bugs.openjdk.org/browse/JDK-8202971.
The test was intermittently failing with timeouts in JDK 11.
Does removing it from ProblemList mean the test does not fail with the symptom of 8202971 anymore?
I'm double-checking because I'm not sure I fully understand the PR description.

@alexmenkov
Copy link
Author

Oh, right. It's socket timeout, not the test timeout. Renamed JBS issue

Nit: Would it better to replace: "fails after ClassNotFoundException" => "fails with ClassNotFoundException" ?

Actually It fails with SocketTimeoutException. The test waits target process to connect, but it happens after target app fails with ClassNotFoundException

@alexmenkov
Copy link
Author

This test was marked in ProblemList with https://bugs.openjdk.org/browse/JDK-8202971. The test was intermittently failing with timeouts in JDK 11. Does removing it from ProblemList mean the test does not fail with the symptom of 8202971 anymore? I'm double-checking because I'm not sure I fully understand the PR description.

I was not able to reproduce 8202971 (400 runs)

@sspitsyn
Copy link
Contributor

Actually It fails with SocketTimeoutException. The test waits target process to connect, but it happens after target app fails with ClassNotFoundException

Okay, thanks.

I was not able to reproduce 8202971 (400 runs)

Okay, thanks.

Copy link
Contributor

@sspitsyn sspitsyn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label May 23, 2025
@alexmenkov
Copy link
Author

/integrate

@openjdk
Copy link

openjdk bot commented May 27, 2025

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

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label May 27, 2025
@openjdk openjdk bot closed this May 27, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels May 27, 2025
@openjdk
Copy link

openjdk bot commented May 27, 2025

@alexmenkov Pushed as commit c110623.

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

@alexmenkov alexmenkov deleted the attach045 branch May 28, 2025 00:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

integrated Pull request has been integrated serviceability serviceability-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

3 participants