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

HTML and LRA folder not getting created after LR scenario execution with Jenkins

      Hi,

      I'm trying to run Load runner scenario using Jenkins using master slave setup. The slave machine setup which has the load runner scenario is as follows

      Windows server 2012 R2 standard, RAM: 16 GB

      In Jenkins my build step is as follows

       

      And post build step

      The Load runner scenario is getting triggered and executed perfectly fine but in the analysing results part the folder LRR and HTML is not getting created but the LRR folder and its results is getting created. Because these folders are not getting created  the LR analysis launcher is failing with file not found exception. Could you please suggest a resolution. PFB the output console info of the build

      Building remotely on server (Kana_Digital_NewController) in workspace D:\Jenkins\workspace\KanaNewDigital
      No emails were triggered.
      [KanaNewDigital] $ cmd /c call C:\WINDOWS\TEMP\jenkins826415970228755588.bat

      D:\Jenkins\workspace\KanaNewDigital>echo DATE:2018-04-12 12:21:26 AEST
      DATE:2018-04-12 12:21:26 AEST

      D:\Jenkins\workspace\KanaNewDigital>exit 0
      [KanaNewDigital] $ D:\Jenkins\workspace\KanaNewDigital\HpToolsLauncher.exe -paramfile props12042018122126463.txt
      "Started..."
      Launcher timeout is 10675199::02:48:05
      Controller Polling Interval: 120 seconds
      PerScenarioTimeout: 00::00:05:00 minutes
      FileSystemTestRunner timeout is 10675199.02:48:05.4775807
      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:\Jenkins\DigitalDemo.lrs
      ============================================================================
      12/04/2018 12:21:26 Running: D:\Jenkins\DigitalDemo.lrs
      Cleaning up the environment...
      Preparing scenario D:\Jenkins\DigitalDemo.lrs for execution.
      Load Generator server connected
      Load Generator server connected
      setting scenario result folder to D:\Jenkins\workspace\KanaNewDigital\cf1002\LRR
      scenario result folder: D:\Jenkins\workspace\KanaNewDigital\cf1002\LRR
      Starting scenario...
      Scenario run has started
      Error: Scenario Execution timeout (0 seconds) passed.
      Error: Scenario Execution timeout ({0} seconds) passed.
      Scenario D:\Jenkins\DigitalDemo.lrs ended after 0:6:0.
      ============================================================================
      Analyzing results...
      closing Controller
      Controller closed
      calling analysis report generator
      EXECUTING ANALYSIS LAUNCHER WITH ARGUMENTS : "D:\JENKINS\WORKSPACE\KANANEWDIGITAL\CF1002\LRR\LRR.LRR" "D:\JENKINS\WORKSPACE\KANANEWDIGITAL\CF1002\LRA\LRA.LRA" "D:\JENKINS\WORKSPACE\KANANEWDIGITAL\CF1002\HTML\HTML.HTML"
      TIME FOR ANALYSIS: 00::00:05:00
      ERROR: UNHANDLED EXCEPTION: SYSTEM.IO.FILENOTFOUNDEXCEPTION: COULD NOT LOAD FILE OR ASSEMBLY 'ANALYSIS.APILIB, VERSION=11.50.0.0, CULTURE=NEUTRAL, PUBLICKEYTOKEN=2F103498D61AA5A7' OR ONE OF ITS DEPENDENCIES. THE SYSTEM CANNOT FIND THE FILE SPECIFIED.
      Error: at LRAnalysisLauncher.Program.Main(String[] args)
      time passed: 00::00:00:00
      Error: Error during Analysis run. See output console for details
      analysis report generator finished
      Error(s) summary:
      0 ignored , 0 errors

      Test PASSED
      Test result: Error
      12/04/2018 12:30:18 Test complete: D:\Jenkins\DigitalDemo.lrs
      -------------------------------------------------------------------------------------------------------
      Cleaning up the environment...
      ================================================
      Run status: Job failed, total tests: 1, succeeded: 0, failures: 0, errors: 1
      Error : D:\Jenkins\DigitalDemo.lrs
      ================================================
      Build step 'Execute HPE tests from file system' changed build result to FAILURE
      Hello 1
      Hello 2
      Recording test results
      RunResultRecorder: didn't find any test results to record
      Email was triggered for: Always
      Sending email for trigger: Always
      Sending email to:
      Finished: FAILURE

          [JENKINS-50756] HTML and LRA folder not getting created after LR scenario execution with Jenkins

          Hi,

          Any updates on this issue?

          Thanks

          Ashwin Unnikrishnan added a comment - Hi, Any updates on this issue? Thanks

          Rolando-Mihai Vlad added a comment - - edited

          Hello Ashwin,

           

          Check if you have Analysis.ApiLib.dll. It is located HPE\LoadRunner\bin. Also, I can see you encountered the following error: "Scenario Execution timeout (0 seconds) passed". This is because you set the Scenario Execution Timeout to 5 minutes and your scenarios execution will exceed that time.

           

          Best regards,

          Vlad Rolando-Mihai

          Rolando-Mihai Vlad added a comment - - edited Hello Ashwin,   Check if you have Analysis.ApiLib.dll. It is located HPE\LoadRunner\bin. Also, I can see you encountered the following error: "Scenario Execution timeout (0 seconds) passed". This is because you set the Scenario Execution Timeout to 5 minutes and your scenarios execution will exceed that time.   Best regards, Vlad Rolando-Mihai

          Daniel Gront added a comment -

          ash23 Is this issue resolved?

          Daniel Gront added a comment - ash23 Is this issue resolved?

          Hi rolandomihaivlad,

          Apologies for the late reply. As a resolution for this issue i tried reinstalling HP load runner version 12.53 patch 3 in the Windows server 2012 R2 standard, But still I'm getting the same error.

          The Analysis.API.dll is present in the HPE\LoadRunner\bin as well as HP\LoadRunner\bin.

          Could you please confirm if Jenkins works fine with load runner version 12.53 patch 3 and do we have to do any additional settings in Windows server 2012 R2 standard specific for Jenkins.

          Thank You

          Ashwin

          Ashwin Unnikrishnan added a comment - Hi rolandomihaivlad , Apologies for the late reply. As a resolution for this issue i tried reinstalling HP load runner version 12.53 patch 3 in the Windows server 2012 R2 standard, But still I'm getting the same error. The Analysis.API.dll is present in the HPE\LoadRunner\bin as well as HP\LoadRunner\bin. Could you please confirm if Jenkins works fine with load runner version 12.53 patch 3 and do we have to do any additional settings in Windows server 2012 R2 standard specific for Jenkins. Thank You Ashwin

          Rolando-Mihai Vlad added a comment - - edited

          Hello Ashwin,

           

           The dll is Analysis.ApiLib.dll, not Analysis.Api.dll. I will check if there is a compatibility issue beween LR 12.53 and Jenkins Plugin.

           

          Regards,

          Rolando

          Rolando-Mihai Vlad added a comment - - edited Hello Ashwin,    The dll is Analysis.ApiLib.dll, not Analysis.Api.dll. I will check if there is a compatibility issue beween LR 12.53 and Jenkins Plugin.   Regards, Rolando

          Hi rolandomihaivlad,

          The Analysis.APi.dll is also present in the same path.

          Regards,

          Ashwin

          Ashwin Unnikrishnan added a comment - Hi rolandomihaivlad , The Analysis.APi.dll is also present in the same path. Regards, Ashwin

          Rolando-Mihai Vlad added a comment - - edited

          Hello Ashwin,

           I tested 12.53 patch 3 on win2012 with jenkins 5.3 on ubuntu 14 and the build passes. Other possible issues could be: analysis.assemblyinfoconstants.dll missing or a corrupted .NET framework. We can have a webex someday if your issue persists.

          Regards,

          Rolando

           

          Rolando-Mihai Vlad added a comment - - edited Hello Ashwin,  I tested 12.53 patch 3 on win2012 with jenkins 5.3 on ubuntu 14 and the build passes. Other possible issues could be: analysis.assemblyinfoconstants.dll missing or a corrupted .NET framework. We can have a webex someday if your issue persists. Regards, Rolando  

          Hi rolandomihaivlad

          As you mentioned the issue was with the .NET framework i had in my server. I reinstalled it and now everything is working fine.

          Thank you for all the help.

          Regards,

          Ashwin

          Ashwin Unnikrishnan added a comment - Hi rolandomihaivlad As you mentioned the issue was with the .NET framework i had in my server. I reinstalled it and now everything is working fine. Thank you for all the help. Regards, Ashwin

            rolandomihaivlad Rolando-Mihai Vlad
            ash23 Ashwin Unnikrishnan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: