JMH should exit with non-zero exit code when failed benchmarks are detected

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: P4
    • None
    • Affects Version/s: None
    • Component/s: tools
    • None
    • jmh

      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.

            Assignee:
            Aleksey Shipilev
            Reporter:
            Aleksey Shipilev
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: