[
https://issues.jenkins-ci.org/browse/JENKINS-13326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161152#comment-161152
]
Kees Hink commented on JENKINS-13326:
-------------------------------------
Looks like the graph adds values in the order of "ID".
Clicking the ID collumn header in the table to sort the rows on ID (ascending)
yields the order "1, 10, 11, ...", and the MLR values are displayed in the
graph in that order.
Renaming my test ID's by adding 100 (so 1 -> 101, 10 -> 110, 22 -> 122 etc.)
fixes the problem.
> Grinder plugin: Mean Response Length in graph is incorrect
> -----------------------------------------------------------
>
> Key: JENKINS-13326
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13326
> Project: Jenkins
> Issue Type: Bug
> Components: plugin
> Environment: Ubuntu Server 9.04
> Reporter: Kees Hink
> Priority: Trivial
> Labels: plugin
> Attachments: jenkins-grinder-screenshot.png
>
>
> In the graph that is generated from a Grinder plugin report, Mean Response
> Lengths appear to be ordered incorrectly: The MRL value for a given test
> number does not always match the MRL value from the table.
> See attached screenshot. Here you can see that for "Test 2", the graph shows
> an MRL of 0, but the table shows it to bo 227k. The table's value is correct
> here.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
