-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8308986: Disable svc tests failing with virtual thread factory #14193
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 lmesnik! A progress list of the required criteria for merging this PR into |
@lmesnik 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
|
/cc serviceability |
@lmesnik |
Webrevs
|
@@ -72,6 +72,7 @@ java/lang/Thread/UncaughtExceptionsTest.java 0000000 generic-all | |||
java/lang/Thread/virtual/GetStackTraceWhenRunnable.java 0000000 generic-all | |||
java/lang/invoke/condy/CondyNestedResolutionTest.java 0000000 generic-all | |||
java/lang/ref/OOMEInReferenceHandler.java 0000000 generic-all | |||
java/util/concurrent/locks/Lock/OOMEInAQS.java 0000000 generic-all |
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 read the comment a bit further up to see where it explains why this section uses "0000000" for the JBS issue. There's a few typos in the text, e.g. "with with" and "test migth". It might be useful to make that text a bit clearer as I'm sure there will be questions on why there aren't JBS issues for tests excluded from running this mode.
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.
Hotspot changes are good.
JDK side seems okay if this is how we are permanently excluding tests from running with virtual threads. Though as Alan states the comments need a little work.
Thanks.
@lmesnik 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 30 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 |
@@ -31,6 +31,8 @@ serviceability/dcmd/thread/PrintConcurrentLocksTest.java 8308033 generic-all | |||
serviceability/dcmd/thread/PrintTest.java 8308033 generic-all | |||
serviceability/dcmd/thread/ThreadDumpToFileTest.java 8308033 generic-all | |||
serviceability/tmtools/jstack/DaemonThreadTest.java 8308033 generic-all | |||
vmTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t001/TestDescription.java 8308985 generic-all | |||
vmTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t002/TestDescription.java 8308985 generic-all |
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.
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.
Reducing noise in the CI is always good. Especially since it takes |
@@ -31,6 +31,8 @@ serviceability/dcmd/thread/PrintConcurrentLocksTest.java 8308033 generic-all | |||
serviceability/dcmd/thread/PrintTest.java 8308033 generic-all | |||
serviceability/dcmd/thread/ThreadDumpToFileTest.java 8308033 generic-all | |||
serviceability/tmtools/jstack/DaemonThreadTest.java 8308033 generic-all | |||
vmTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t001/TestDescription.java 8308985 generic-all | |||
vmTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t002/TestDescription.java 8308985 generic-all |
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.
|
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 modulo my comment.
It is up to you to decide what bug number to use in the Hotspot problem list.
Also, there are more failing tests because of this issue. For instance:
vmTestbase/nsk/jdi/VirtualMachine/instanceCounts/instancecounts001/instancecounts001.java
vmTestbase/nsk/jdi/ReferenceType/instances/instances001/instances001.java
vmTestbase/nsk/jdi/stress/serial/mixed002/TestDescription.java
vmTestbase/nsk/jdi/stress/serial/heapwalking002/TestDescription.java
Thanks,
Serguei
I've excluded more tests, changed bugid and updated comments. |
I've been trying to figure out what java/util/concurrent/locks/Lock/OOMEInAQS.java |
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.
Thumbs up. Quite a few tests now for 8308978.
test/jdk/ProblemList-Virtual.txt
Outdated
## There is no goal to run all test with virtual test thread factory. | ||
## So any test migth be added as incompatible, the bug is not required. | ||
## So any test might be added as incompatible, the bug is not required. |
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.
typo: s/bug/bug-ID/
vmTestbase/nsk/jdi/VirtualMachine/instanceCounts/instancecounts002/TestDescription.java has also shown up in the CI with same failure mode as the others... |
/integrate |
Going to push as commit 327733c.
Your commit was automatically rebased without conflicts. |
Disable test
java/util/concurrent/locks/Lock/OOMEInAQS.java
Test provokes OOME and might catch it in an unexpected location. It looks like an issue similar to https://bugs.openjdk.org/browse/JDK-8298066. However, generally the OOME might be thrown mount/umount or in unparker thread. There are no plans to fix such tests to be able to pass with virtual threads now.
Also, disable
mTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t001/TestDescription.java
vmTestbase/nsk/jvmti/scenarios/allocation/AP04/ap04t002/TestDescription.java
because of https://bugs.openjdk.org/browse/JDK-8308985
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/14193/head:pull/14193
$ git checkout pull/14193
Update a local copy of the PR:
$ git checkout pull/14193
$ git pull https://git.openjdk.org/jdk.git pull/14193/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 14193
View PR using the GUI difftool:
$ git pr show -t 14193
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/14193.diff
Webrev
Link to Webrev Comment