jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
Signup
Mojo's Chronos Maven Plugins
  • Mojo's Chronos Maven Plugins
  • MCHRONOS-48

Save history does not work

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Cannot Reproduce
  • Affects Version/s: 1.0
  • Fix Version/s: None
  • Component/s: JMeter plugin
  • Labels:
    None
  • Number of attachments :
    0

Description

It seems that the history keeps getting overwritten. If I run multiple tests in a row, it only generates 1 history XML file. The content of the file is changing after each run, so it obviously reuses the same timestamp and therefore overwrites the same file.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
John Nonak added a comment - 04/Jul/12 7:10 AM

My current work around is as follow:

  • Clean before each run
  • Save the history within the default folder (under "target")
  • Add an Ant "copy" task to copy the history file to an external folder (in the root of the project)
  • Configure the history report to read files from the external folder
Show
John Nonak added a comment - 04/Jul/12 7:10 AM My current work around is as follow: Clean before each run Save the history within the default folder (under "target") Add an Ant "copy" task to copy the history file to an external folder (in the root of the project) Configure the history report to read files from the external folder
Hide
Permalink
Kent Sølvsten added a comment - 09/Jul/12 6:04 AM

I find this really odd.

The filename should be something like history-*************.xml, with a lot of numbers representing System.currenttimemillis() at the time that the testrun was started.

First: Are You aware that You do not need to copy with an ant task. By configuring historydir, You can change it to eg $

{basedir}

/chronos-history instead of using the default (which saves history under target). You might argue that the default should be changed.

Second: Are You certain that the content of the historyfile is really changed, and not just the timestamp in the filesystem? If You invoke 'mvn install' several times, there may only be a single testrun. If the jmeter output is already there, it will only be regenerated, if the jmeter scriptfile '.jxm' is changed. This is to avoid running the perofrmancetest twice, if the user runs 'mvn install site'. So what You might see, is chronos creating a historyfile representing the exact same testrun twice - and thus reusing the timestamp.

Show
Kent Sølvsten added a comment - 09/Jul/12 6:04 AM I find this really odd. The filename should be something like history-*************.xml, with a lot of numbers representing System.currenttimemillis() at the time that the testrun was started. First: Are You aware that You do not need to copy with an ant task. By configuring historydir, You can change it to eg $ {basedir} /chronos-history instead of using the default (which saves history under target). You might argue that the default should be changed. Second: Are You certain that the content of the historyfile is really changed, and not just the timestamp in the filesystem? If You invoke 'mvn install' several times, there may only be a single testrun. If the jmeter output is already there, it will only be regenerated, if the jmeter scriptfile '.jxm' is changed. This is to avoid running the perofrmancetest twice, if the user runs 'mvn install site'. So what You might see, is chronos creating a historyfile representing the exact same testrun twice - and thus reusing the timestamp.
Hide
Permalink
Simon Vogensen added a comment - 19/Apr/13 4:45 AM

John has not replied in 5 months. We conclude it may have been a user problem?

Show
Simon Vogensen added a comment - 19/Apr/13 4:45 AM John has not replied in 5 months. We conclude it may have been a user problem?

People

  • Assignee:
    Simon Vogensen
    Reporter:
    John Nonak
Vote (0)
Watch (4)

Dates

  • Created:
    04/Jul/12 6:39 AM
    Updated:
    19/Apr/13 4:45 AM
    Resolved:
    19/Apr/13 4:45 AM
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.