CODETOOLS-7903086: jcstress: Deadlock testing mode

[shipilev]

A few samples, notably DiningPhilosophers and ProducerConsumer are actually testing for multi-actor deadlock. It is now faked by using the @Arbiter and default (continuous) mode, but it comes with a few drawbacks.

First, it is kludgy. Second, that mode runs @Actor once per @State, and so deadlock opportunity is rather narrow.

Instead, we should be having a special deadlock mode.

---

Progress

• [x] Change must not contain extraneous whitespace
• [ ] Change must be properly reviewed

Issue

• CODETOOLS-7903086: jcstress: Deadlock testing mode

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jcstress pull/110/head:pull/110
$ git checkout pull/110

Update a local copy of the PR:
$ git checkout pull/110
$ git pull https://git.openjdk.java.net/jcstress pull/110/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 110

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jcstress/pull/110.diff

[bridgekeeper[bot]]

:wave: Welcome back shade! 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.

[bridgekeeper[bot]]

@shipilev This pull request has been inactive for more than 8 weeks and will be automatically closed if another 8 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

[bridgekeeper[bot]]

@shipilev This pull request has been inactive for more than 16 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the /open pull request command.