Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42476

PC client exits too soon

XMLWordPrintable

      Frequently my HP plugin exits before the load test is actually done. This causes some of my post-run scripts to fail.

      My job is configured to collate and analyze.

      I noticed a difference in the plugin output between a successful an unsuccessful run.

      Unsuccessful:
      Run started (TestID: 4802, RunID: 6790, TimeslotID: 4276)

      Set HP_RUN_ID Env Variable to 6790
      RunID: 6790 - State = Initializing
      RunID: 6790 - State = Running
      RunID: 6790 - State = Stopping
      View report: http://myserver:8080/job/myjob/153/artifact/performanceTestsReports/pcRun6790/Report.html
      Logout succeeded
      Result Status (PC RunID: 6790): SUCCESS

      Successful:
      Run started (TestID: 4802, RunID: 6796, TimeslotID: 4297)

      Set HP_RUN_ID Env Variable to 6796
      RunID: 6796 - State = Initializing
      RunID: 6796 - State = Running
      RunID: 6796 - State = Collating Results
      RunID: 6796 - State = Creating Analysis Data
      RunID: 6796 - State = Finished
      Publishing run report
      View report: http://myserver:8080/job/myjob/154/artifact/performanceTestsReports/pcRun6796/Report.html
      Logout succeeded
      Result Status (PC RunID: 6796): SUCCESS

      Notice how the last state of the successful one is "Finished?" The unsuccessful one doesn't even show the collate and analyze steps. This seems to be a pretty clear pattern across multiple executions.

      thanks

            bemh Hanan Bem
            john_gregg John Gregg
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: