jmeter-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 62822] New: Default Summary Report min/max values are inaccurate
Date Fri, 12 Oct 2018 20:08:30 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=62822

            Bug ID: 62822
           Summary: Default Summary Report min/max values are inaccurate
           Product: JMeter
           Version: 3.3
          Hardware: PC
            Status: NEW
          Severity: trivial
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: aj.johnson@zenplanner.com
  Target Milestone: JMETER_5.1

Created attachment 36195
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=36195&action=edit
A screenshot of the Summary Report with inaccurate display values

In the Summary Report, when no samples have been processed (i.e., after
clearing the report) the displayed minimum and maximum values are inaccurate.
The minimum displays as the largest positive long integer value
(9223372036854775807) while the maximum displays as the lowest negative long
integer value(-9223372036854775808).

This is due to the Calculator class' initial values for the minimum and maximum
instance variables:

    private long maximum = Long.MIN_VALUE;

    private long minimum = Long.MAX_VALUE;

In reality, when no samples have been processed, all values related to the
Calculator's dataset should be undefined. Other values are initialized as 0,
and therefore display as 0 instead of some seemingly random value in the UI.
The min/max should likely also *display* as 0 when no samples have been
processed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
Mime
View raw message