Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-8281

It seems that when one jtl-file is marked as FAILURE all the following is marked as FAILURE no matter the error rate?

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • jmeter
    • None
    • Windows XP, WebSphere AppServer 6.1, Hudson 1.384, Performance plugin 1.3

      Performance: No threshold configured for making the test unstable Performance: Percentage of errors greater or equal than 1% sets the build as failure Performance: Recording JMeter reports '*/.jtl'
      Performance: Parsing JMeter report file 2010-12-09_14-29-13(booking).jtl
      Performance: Parsing JMeter report file 2010-12-09_14-33-43(booking).jtl
      Performance: Parsing JMeter report file 2010-12-09_14-38-00(booking).jtl
      Performance: Parsing JMeter report file 2010-12-10_10-11-06(booking).jtl
      Performance: File 2010-12-09_14-29-13(booking).jtl reported 0.9009009009009009% of errors during the tests. Build status is: SUCCESS
      Performance: File 2010-12-09_14-33-43(booking).jtl reported 1.8518518518518516% of errors during the tests. Build status is: FAILURE
      Performance: File 2010-12-09_14-38-00(booking).jtl reported 0.9009009009009009% of errors during the tests. Build status is: FAILURE
      Performance: File 2010-12-10_10-11-06(booking).jtl reported 14.705882352941178% of errors during the tests. Build status is: FAILURE


      The first file is parsed and set to SUCCESS as the error threshold is 1%.
      The next file is failed as the error rate is >1%.
      The third file should be a SUCCESS as the error rate is <1% but it is marked as FAILURE?

      I've seen this scenario where the first file failed and even though the next 10 files had an error rate of 0.0% they were still marked as FAILURE. Only when I cleared the workspace and ran the job again the file was marked as SUCCESS.

            vergnes vergnes
            hapco hapco
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: