P4
As reported here:
http://mail.openjdk.java.net/pipermail/jmh-dev/2015-February/001684.html
The subject says it all: we need to communicate the non-zero code when there are
problems even if failOnError is disabled.
http://mail.openjdk.java.net/pipermail/jmh-dev/2015-February/001684.html
The subject says it all: we need to communicate the non-zero code when there are
problems even if failOnError is disabled.
- relates to
-
CODETOOLS-7901297 JMH CLI runner should set non-zero exit code when failOnError(true) and benchmarks fail
-
- Closed
-