-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8357282: Test vmTestbase/nsk/jvmti/AttachOnDemand/attach045/TestDescription.java fails after ClassNotFoundException #25366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
👋 Welcome back amenkov! A progress list of the required criteria for merging this PR into |
|
@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: 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
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 |
|
@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
|
|
/label add serviceability |
|
@alexmenkov |
lmesnik
left a comment
There was a problem hiding this 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); |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for explanation.
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" ? |
|
This test was marked in ProblemList with https://bugs.openjdk.org/browse/JDK-8202971. |
Actually It fails with SocketTimeoutException. The test waits target process to connect, but it happens after target app fails with ClassNotFoundException |
I was not able to reproduce 8202971 (400 runs) |
Okay, thanks.
Okay, thanks. |
sspitsyn
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
|
/integrate |
|
Going to push as commit c110623.
Your commit was automatically rebased without conflicts. |
|
@alexmenkov Pushed as commit c110623. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
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
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25366/head:pull/25366$ git checkout pull/25366Update a local copy of the PR:
$ git checkout pull/25366$ git pull https://git.openjdk.org/jdk.git pull/25366/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 25366View PR using the GUI difftool:
$ git pr show -t 25366Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25366.diff
Using Webrev
Link to Webrev Comment