-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8210558: serviceability/sa/TestJhsdbJstackLock.java fails to find '^\s+- waiting to lock <0x[0-9a-f]+> \(a java\.lang\.Class ...' #6689
Conversation
👋 Welcome back cjplummer! A progress list of the required criteria for merging this PR into |
@plummercj 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. |
I got some test failures when doing a large number of test runs. Need to investigate. Withdrawing for now. |
These test failures I am occasionally seeing also occur without my changes and appear to be due to OSX host issues, so I'm reopening this PR. |
@plummercj 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 51 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 |
Thanks for the reviews Serguei and Kevin! |
/integrate |
Going to push as commit 587e540.
Your commit was automatically rebased without conflicts. |
@plummercj Pushed as commit 587e540. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The issue appears to be due to running jstack before allowing the 4 threads created by
LingeredAppWithLock
to fully start up and reach their blocking or timed wait state. With this fixLingeredAppWithLock.main()
now waits until the threads have reached the blocking or timed wait state before calling intoLingeredApp.main()
.Tests that use
LingeredAppWithLock
callLingeredApp.startApp()
, which will first launchLingeredAppWithLock
and then block until the lock file is touched. This blocking/waiting is done the call towaitAppReady()
, which will be called beforeLingeredApp.startApp()
returns. The lock file is not touched untilLingeredApp.main()
is called, and it is not called until afterLingeredAppWithBloc.main()
has already verified the state of all the threads. Thus by the timeLingeredApp.startApp()
returns, we can be sure that the threads started byLingeredAppWithLock.main()
are in the desired state.Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6689/head:pull/6689
$ git checkout pull/6689
Update a local copy of the PR:
$ git checkout pull/6689
$ git pull https://git.openjdk.java.net/jdk pull/6689/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6689
View PR using the GUI difftool:
$ git pr show -t 6689
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6689.diff