Flaky test or race condition - `ParallelSpec#@ResourceLock with only READ allows parallel execution of data-driven features`

Describe the bug

I've seen the
ParallelSpec#@ResourceLock with only READ allows parallel execution of data-driven features test failing with

    Condition not satisfied:

    atomicInteger.get() == 3
    |             |     |
    3             1     false
        at apackage.ASpec.writeA(Script_9186d4f70d72d15ebba0478d4c746046.groovy:14)

in master lately in GitHub Action run.

I tried to reproduce by adding @RepeatUntilFailure (nice addition).
First try didn't reproduce in about 1000 runs.
Second try reproced after 4 iterations with the same failure.
Third try didn't reproduce again in about 1000 runs.

So it seems there is some race condition somewhere.

To Reproduce

Add @RepeatUntilFailure to the test and try to make it fail

Expected behavior

No assertion error

Actual behavior

Occasionally assertion error

Java version

Seen with Java 8 and Java 17.
Seen with Groovy 2.5 and Groovy 3.0 variant.

Buildtool version

Gradle as configured in master

What operating system are you using

Windows

Start with the ParallelSpec#@ResourceLock with only READ allows parallel execution of data-driven features test and reproduce it by adding @RepeatUntilFailure, using the Gradle setup on master. Compare repeated runs on the reported Java and Groovy variants; done means the intermittent assertion failure is understood and the test no longer fails in repeated runs.