Originally reported here:
http://mail.openjdk.java.net/pipermail/jmh-dev/2016-January/002122.html
The solution would be to make the lock file world-writeable somehow.
http://mail.openjdk.java.net/pipermail/jmh-dev/2016-January/002122.html
The solution would be to make the lock file world-writeable somehow.
- relates to
-
JDK-8193391 Unable to acquire the JMH lock
-
- Closed
-
-
CODETOOLS-7901013 JMH should safeguard against the concurrent execution with file lock
-
- Closed
-