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
JDK-8286789: Test forceEarlyReturn002.java timed out #15301
Conversation
👋 Welcome back amenkov! A progress list of the required criteria for merging this PR into |
@alexmenkov The following label will be automatically applied to this pull request:
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. |
Webrevs
|
...se/nsk/jdwp/ThreadReference/ForceEarlyReturn/forceEarlyReturn002/libforceEarlyReturn002a.cpp
Outdated
Show resolved
Hide resolved
@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 67 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 |
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.
This looks okay.
There is still a question why the test failed intermittently.
Let's see if it can be reproduced again.
Thanks,
Serguei
Infinite loops are not good to have so the test adjustment seems fine in that regard. But I can't see how using the virtual thread factory could trigger a problem with this code. |
It's not clear to me as well. |
/integrate |
Going to push as commit c90cd2c.
Your commit was automatically rebased without conflicts. |
@alexmenkov Pushed as commit c90cd2c. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This is an attempt to fix suspicious code in the forceEarlyReturn002.java and un-problemlist it to see if the problem appear again.
The test fails in "virtual thread factory" mode with timeout for unclear reason after it finished testing and performs cleanup process (debugger sends debuggee a command to exit, but debuggee doesn't receive the command).
This is the only test which has this intermittent communication failures.
The test was problem-listed, I was not able to reproduce the issue with 1000+ runs.
Debuggee creates a thread which executes tight infinite loop in native code (in "virtual thread factory" mode it's pinned virtual thread).
The fix adds delays in the loop and adds new command to exit from native method after testing.
Testing: 100 runs in "virtual thread factory" mode on all Oracle supported platforms.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15301/head:pull/15301
$ git checkout pull/15301
Update a local copy of the PR:
$ git checkout pull/15301
$ git pull https://git.openjdk.org/jdk.git pull/15301/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15301
View PR using the GUI difftool:
$ git pr show -t 15301
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15301.diff
Webrev
Link to Webrev Comment