Summary: | Saved Aggregate Report is Different from original when reloaded | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | udele <udele.malabanan> |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0.0 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Attachments: | Sample jtl file for calculations |
Description
udele
2004-06-09 21:41:28 UTC
Could you perhaps attach a sample JTL file that shows the problem? Created attachment 11814 [details]
Sample jtl file for calculations
I've attached a sample jtl file. Out of curiosity I opened up the jtl file in two separate Aggregate reports in a new Test Plan. The only difference between the two reports in the new plan seems to be the Total in the Rate column. The difference appears more pronounced between an aggregate report that is generated directly from a test run and a saved report. Can't see any obvious problems when loading the JTL into two different Aggregate Reports - apart from an extraneous "/" in the Totals Rate column. Looking at the data shows that the /login URLs are different from the others, in that they include two sub-results each. This is because /login returns a 302 - redirect temporary. This may be the cause. If you can recode the test to avoid the redirect, it would be interesting to see if this changed the calculations. Could you give a bit more information on what figures you think are wrong? Thank you seb! Once I stopped following redirects in my test plan, the problem went away. For the majority of the time, the rate was being calculated differently for the /login page. Occasionally, I would see the min, max, and average off too, but I can't reproduce that as easily for the same page. I would like to be able to follow redirects (specifically for viewing in my results tree), but I can live without it for now. Finally discovered the problem: when subresults are initially added to main result, the elapsed time for the main result is accumulated. However, when the results are read in from a file, this calculation has already been done. Fixed in 2.1 branch for both old and new XML format result files [does not affect CSV results, as subresults are not saved] This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1384 |