You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2018/10/12 20:08:30 UTC
[Bug 62822] New: Default Summary Report min/max values are
inaccurate
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.
[Bug 62822] Default Summary Report min/max values are inaccurate
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62822
--- Comment #3 from Felix Schumacher <fe...@internetallee.de> ---
Date: Tue Oct 16 18:50:09 2018
New Revision: 1844043
URL: http://svn.apache.org/viewvc?rev=1844043&view=rev
Log:
Unused import
Followup to r1844031
Render uninitialized min and max values in Summary Report as `#N/A`
In the Summary Report min and max values are initialized with
`Long#MAX_VALUE` and `Long#MIN_VALUE` to work easily with them.
Those initial values are looking weird in the rendered view.
Hide them by replacing the extrema by the text `#N/A`.
Relates to #407 on github
Bugzilla Id: 62822
Modified:
jmeter/trunk/src/components/org/apache/jmeter/visualizers/SummaryReport.java
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 62822] Default Summary Report min/max values are inaccurate
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62822
--- Comment #4 from AJ Johnson <aj...@zenplanner.com> ---
(In reply to Felix Schumacher from comment #2)
> Will be in the next version, which is probably 5.1.
>
> Could you test the next nightly, if it works for you?
>
> Date: Tue Oct 16 17:33:44 2018
> New Revision: 1844031
>
> URL: http://svn.apache.org/viewvc?rev=1844031&view=rev
> Log:
> Render uninitialized min and max values in Summary Report as `#N/A`
>
> In the Summary Report min and max values are initialized with
> `Long#MAX_VALUE` and `Long#MIN_VALUE` to work easily with them.
>
> Those initial values are looking weird in the rendered view.
> Hide them by replacing the extrema by the text `#N/A`.
>
> Closes #407 on github
> Bugzilla Id: 62822
>
> Date: Tue Oct 16 17:36:39 2018
> New Revision: 1844032
>
> URL: http://svn.apache.org/viewvc?rev=1844032&view=rev
> Log:
> Add missing License header
>
> Followup to r1844031
>
> Render uninitialized min and max values in Summary Report as `#N/A`
>
> In the Summary Report min and max values are initialized with
> `Long#MAX_VALUE` and `Long#MIN_VALUE` to work easily with them.
>
> Those initial values are looking weird in the rendered view.
> Hide them by replacing the extrema by the text `#N/A`.
>
> Closes #407 on github
> Bugzilla Id: 62822
Tested it today on latest build, and it looks solid to me.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 62822] Default Summary Report min/max values are inaccurate
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62822
Felix Schumacher <fe...@internetallee.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #2 from Felix Schumacher <fe...@internetallee.de> ---
Will be in the next version, which is probably 5.1.
Could you test the next nightly, if it works for you?
Date: Tue Oct 16 17:33:44 2018
New Revision: 1844031
URL: http://svn.apache.org/viewvc?rev=1844031&view=rev
Log:
Render uninitialized min and max values in Summary Report as `#N/A`
In the Summary Report min and max values are initialized with
`Long#MAX_VALUE` and `Long#MIN_VALUE` to work easily with them.
Those initial values are looking weird in the rendered view.
Hide them by replacing the extrema by the text `#N/A`.
Closes #407 on github
Bugzilla Id: 62822
Date: Tue Oct 16 17:36:39 2018
New Revision: 1844032
URL: http://svn.apache.org/viewvc?rev=1844032&view=rev
Log:
Add missing License header
Followup to r1844031
Render uninitialized min and max values in Summary Report as `#N/A`
In the Summary Report min and max values are initialized with
`Long#MAX_VALUE` and `Long#MIN_VALUE` to work easily with them.
Those initial values are looking weird in the rendered view.
Hide them by replacing the extrema by the text `#N/A`.
Closes #407 on github
Bugzilla Id: 62822
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 62822] Default Summary Report min/max values are inaccurate
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62822
Felix Schumacher <fe...@internetallee.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
--- Comment #1 from Felix Schumacher <fe...@internetallee.de> ---
Added a pull request on Github under https://github.com/apache/jmeter/pull/407
Initial values for min and max will be displayed as "#N/A".
--
You are receiving this mail because:
You are the assignee for the bug.