Details

    • Similar Issues:

      Description

      We are unable to execute a LoadRunner test from Jenkins. The scenario and script are local on the node. Here is the output log:

       
      Started by user
      [EnvInject] - Loading node environment variables.
      Building remotely on
      Windows_ptglrc4
      in workspace D:\workspace\vdp-vertical\performance-lr-it
      Disk space threshold is set to :0Gb
      Checking disk space Now
      Total Disk Space Available is: 33Gb
      Node Name: Windows_ptglrc4
      Running Prebuild steps
      [performance-lr-it] $ D:\workspace\vdp-vertical\performance-lr-it\HpToolsLauncher.exe -paramfile props16062017122442386.txt
      "Started..."
      Launcher timeout is 00::00:00:30
      Controller Polling Interval: 30 seconds
      PerScenarioTimeout: 00::00:30:00 minutes
      FileSystemTestRunner timeout is 00:00:30
      Mc connection info is - Mc HostAddress: , McPort: 8080, Username: , UseSSL: 0, UseProxy: 0, ProxyType: 0, ProxyAddress: , ProxyPort: 0, ProxyAuth: 0, ProxyUser:
      1 tests found:
      D:\CI\Test.lrs
      ============================================================================
      16/06/2017 12:24:42 Running: D:\CI\Test.lrs
      Cleaning up the environment...
      wlrun killed
      Preparing scenario D:\CI\Test.lrs for execution.
      Load Generator ptglrc4 connected
      setting scenario result folder to D:\workspace\vdp-vertical\performance-lr-it\6d8cd8\LRR
      scenario result folder: D:\workspace\vdp-vertical\performance-lr-it\6d8cd8\LRR
      Starting scenario...
      Scenario run has started
      ==============
      Job timed out!
      ==============
      Error: ==============
      Job timed out!
      ==============
      Test result: Error
      16/06/2017 12:25:55 Test complete: D:\CI\Test.lrs
      -------------------------------------------------------------------------------------------------------
      Cleaning up the environment...
      ================================================
      Run status: Job failed, total tests: 1, succeeded: 0, failures: 0, errors: 1
      Build step 'Execute HP tests from file system' changed build result to FAILURE
      Recording test results
      RunResultRecorder: didn't find any test results to record
      Started calculate disk usage of build
      Finished Calculation of disk usage of build in 0 seconds
      Started calculate disk usage of workspace
      Finished Calculation of disk usage of workspace in 0 seconds
      Finished: FAILURE

        Attachments

          Activity

          Hide
          dchan Don Chan added a comment -

          Sometimes it does run but the test doesn't seem to be executing. 

           
          16/06/2017 13:23:44 Running: D:\CI\Test.lrs
          Cleaning up the environment...
          Preparing scenario D:\CI\Test.lrs for execution.
          Load Generator localhost connected
          setting scenario result folder to D:\workspace\vdp-vertical\performance-lr-it\d70db0\LRR
          scenario result folder: D:\workspace\vdp-vertical\performance-lr-it\d70db0\LRR
          Starting scenario...
          Scenario run has started
          Scenario D:\CI\Test.lrs ended after 0:0:9.
          ============================================================================
          Analyzing results...
          closing Controller
          Controller closed
          calling analysis report generator
          executing Analysis launcher with arguments : "D:\workspace\vdp-vertical\performance-lr-it\d70db0\LRR\LRR.lrr" "D:\workspace\vdp-vertical\performance-lr-it\d70db0\LRA\LRA.lra" "D:\workspace\vdp-vertical\performance-lr-it\d70db0\HTML\HTML.html"
          time for analysis: 00::00:30:00
          starting analysis launcher
          creating analysis COM object
          creating analysis session
          analysis session created
          creating HTML reports
          HTML reports created
          loading errors, if any
          Gathering Run statistics
          closing session
          SLA report:
          calculating SLA
          SLA calculation done
          WholeRunRules : 1

          Show
          dchan Don Chan added a comment - Sometimes it does run but the test doesn't seem to be executing.    16/06/2017 13:23:44 Running: D:\CI\Test.lrs Cleaning up the environment... Preparing scenario D:\CI\Test.lrs for execution. Load Generator localhost connected setting scenario result folder to D:\workspace\vdp-vertical\performance-lr-it\d70db0\LRR scenario result folder: D:\workspace\vdp-vertical\performance-lr-it\d70db0\LRR Starting scenario... Scenario run has started Scenario D:\CI\Test.lrs ended after 0:0:9. ============================================================================ Analyzing results... closing Controller Controller closed calling analysis report generator executing Analysis launcher with arguments : "D:\workspace\vdp-vertical\performance-lr-it\d70db0\LRR\LRR.lrr" "D:\workspace\vdp-vertical\performance-lr-it\d70db0\LRA\LRA.lra" "D:\workspace\vdp-vertical\performance-lr-it\d70db0\HTML\HTML.html" time for analysis: 00::00:30:00 starting analysis launcher creating analysis COM object creating analysis session analysis session created creating HTML reports HTML reports created loading errors, if any Gathering Run statistics closing session SLA report: calculating SLA SLA calculation done WholeRunRules : 1
          Hide
          yafim_kazak Yafim Kazak added a comment -

          Hi,
          it seems that you've put your scenario timeout to 30 seconds. could you please verify your job settings (Job timeout units are in seconds) to see the configured timeout?

          Show
          yafim_kazak Yafim Kazak added a comment - Hi, it seems that you've put your scenario timeout to 30 seconds. could you please verify your job settings (Job timeout units are in seconds) to see the configured timeout?
          Hide
          dchan Don Chan added a comment -

          OK. what value do you suggest trying? We also have a ticket opened with our support provider, Orasi. They aren't able to run a test either.

          Show
          dchan Don Chan added a comment - OK. what value do you suggest trying? We also have a ticket opened with our support provider, Orasi. They aren't able to run a test either.
          Hide
          yafim_kazak Yafim Kazak added a comment -

          First please try it empty - if that works, then you simply need to use longer timeout.
          For example, if your scenario takes less then 10 min -> put 600 in the box.

          If problem isn't resolved -> please upload your job config files - either here or at: kazak [at] hpe.com.
          the config files reside at:
          <jenkins folder>\jobs\<job name>\config.xml

          Thanks ahead,
          Yafim.

          Show
          yafim_kazak Yafim Kazak added a comment - First please try it empty - if that works, then you simply need to use longer timeout. For example, if your scenario takes less then 10 min -> put 600 in the box. If problem isn't resolved -> please upload your job config files - either here or at: kazak [at] hpe.com. the config files reside at: <jenkins folder>\jobs\<job name>\config.xml Thanks ahead, Yafim.
          Hide
          yafim_kazak Yafim Kazak added a comment -

          Don Chan hi any update? if problem persists please send me the files written above.

          Show
          yafim_kazak Yafim Kazak added a comment - Don Chan hi any update? if problem persists please send me the files written above.
          Hide
          yafim_kazak Yafim Kazak added a comment -

          Please reopen if issue persists .

          Show
          yafim_kazak Yafim Kazak added a comment - Please reopen if issue persists .
          Hide
          dchan Don Chan added a comment -

          Thanks for your help. I have seemed to have got it working again. The problem was increasing the "Scenario Execution Timeout". The instructional text says it should be in minutes, but its actually in seconds!

          Show
          dchan Don Chan added a comment - Thanks for your help. I have seemed to have got it working again. The problem was increasing the "Scenario Execution Timeout". The instructional text says it should be in minutes, but its actually in seconds!

            People

            • Assignee:
              yafim_kazak Yafim Kazak
              Reporter:
              dchan Don Chan
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: