JMeter performance test isnt correctly checked against errorFailedThreshold and errorUnstableThreshold

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: performance-plugin
    • None
    • Environment:
      Jenkins ver. 1.605
      Performance plugin 1.13

      JMeter performance test isnt correctly checked against errorFailedThreshold and errorUnstableThreshold. The limits is set and the error rate is below the limit. Hence it should pass. Those are the only two fields I send to the PerformancePlugin. See log below:

      ---------------------
      09:40:45 summary = 13135 in 60.2s = 218.2/s Avg: 37 Min: 3 Max: 1086 Err: 31 (0.24%)
      09:40:45 Tidying up ... @ Tue Jun 21 09:40:45 CEST 2016 (1466494845438)
      09:40:45 ... end of run
      09:40:49 FAILED
      09:40:49
      09:40:49 FAILURE: Build failed with an exception.
      09:40:49
      09:40:49 * What went wrong:
      09:40:49 Execution failed for task ':jmeterRun'.
      09:40:49 > There were test failures. See the jmeter logs for details.
      09:40:49
      09:40:49 * Try:
      09:40:49 Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
      09:40:49
      09:40:49 BUILD FAILED
      09:40:49
      09:40:49 Total time: 1 mins 11.787 secs
      09:40:49 Build step 'Invoke Gradle script' changed build result to FAILURE
      09:40:49 Build step 'Invoke Gradle script' marked build as failure
      09:40:49 Performance: Percentage of errors greater or equal than 1% sets the build as unstable
      09:40:49 Performance: Percentage of errors greater or equal than 2% sets the build as failure
      09:40:49
      09:40:49
      09:40:49
      09:40:49 Finished: FAILURE

            Assignee:
            Philippe Mouawad
            Reporter:
            Jonas Wijk
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: