RFR: 7902982: jcstress: Add samples for some mutex algorithms [v10]

[Vladimir Sitnikov]

On Tue, 29 Jun 2021 15:41:03 GMT, mmirwaldt for openjdk <github.com+86246875+mmirwaldt-openjdk at openjdk.org> wrote:

>> I have implemented 3 more samples:
>> *) the NoAlgorithm sample should show users of JCStress how they can define a critical section in a simple way
>> *) one sample for the Peterson's algorithm 
>> *) one sample for the Dekker's algorithm 
>> I have translated the pseudo code implementations of the English wikipedia articles into Java.
>> I have also tried out those examples: they compile and they run without any problems.
>
> mmirwaldt for openjdk has updated the pull request incrementally with three additional commits since the last revision:
> 
>  - gave state annotation its own line
>  - reorganized the imports
>  - changed the outcomes of the mutex samples

jcstress-samples/src/main/java/org/openjdk/jcstress/samples/concurreny/mutex/Mutex_01_PetersonAlgorithm.java line 46:

> 44: @JCStressTest
> 45: @Outcome(id = {"1, 2", "2, 1"}, expect = ACCEPTABLE, desc = "Sequential execution.")
> 46: @Outcome(id = "1, 1", expect = ACCEPTABLE_INTERESTING, desc = "Both actors came up with the same value: lock failure.")@State

Is lock failure "acceptable"? I would say it should be forbidden.

jcstress-samples/src/main/java/org/openjdk/jcstress/samples/concurreny/mutex/Mutex_02_DekkerAlgorithm.java line 46:

> 44: @JCStressTest
> 45: @Outcome(id = {"1, 2", "2, 1"}, expect = ACCEPTABLE, desc = "Sequential execution.")
> 46: @Outcome(id = "1, 1", expect = ACCEPTABLE_INTERESTING, desc = "Both actors came up with the same value: lock failure.")@State

Please move `@State` annotation to its own line.

-------------

PR: https://git.openjdk.java.net/jcstress/pull/85