Load runner job is failing in jenkins

 

I have installed the Load Runner in one of the Windows Server and I have done integration with Jenkins. When I run job from jenkins its giving following error .

Jenkin is installed in Linux Server. 

Could you please hel me to fix this issue ? 

Error Message 100

Started by user admin
Running as SYSTEM
Building on the built-in node in workspace /var/lib/jenkins/workspace/manjutest4
NOTE : The test parameters and their values are printed by default in both Console Output and Results###.xml. You can disable this behavior by defining a job-level parameter UFT_PRINT_TEST_PARAMS as boolean and set it to false.
[manjutest4] $ /var/lib/jenkins/workspace/manjutest4/HpToolsLauncher.exe -paramfile props03022023130359728.txt -encoding UTF-8
/var/lib/jenkins/workspace/manjutest4/HpToolsLauncher.exe: /var/lib/jenkins/workspace/manjutest4/HpToolsLauncher.exe: cannot execute binary file
Launch return code 126
Build step 'Execute Micro Focus tests from file system' changed build result to FAILURE
RunResultRecorder: no results xml File provided
Finished: FAILURE

Thanks and regards,
Manjunath

Tags:

Top Replies

  • Suggested Answer

    0  

      , What kind of integration do you use?  The error indicates, that it can not start the Windows executable HpToolsLauncher.exe. That looks reasonable for me when your Jenkins server is Linux.

    I use LRE and integrate from Jenkins with the Micro Focus Application Automation Tools. This integration is pure Java based via HTTP(S) to LRE.

    When you use LRP, checkout point 6 of Prerequisites (Create an execution node).

    How to ask questions

    Reward contributions via likes or 'verified answers'

  • 0   in reply to JHF Remmelzwaal

    Hello JHF,

    Good day , Thank you very much for giving the reply , 

    Jenkins is installed on the Aws Linux Server, HP load Runner 2022 Free version  is installed on windows 2016 Server . I have installed the Micro Focus Application Automation Tools  plugin in Jenkins.

    We have given the path of the scenario file  (C:\LoadRunner\Scenario1.lrs)  of the LR in Jenkins build step  and  when we build the task which will give the below mentioned error.

    ERROR MESSAGE: 

    Started by user admin
    Running as SYSTEM
    Building on the built-in node in workspace /var/lib/jenkins/workspace/manjutest4
    NOTE : The test parameters and their values are printed by default in both Console Output and Results###.xml. You can disable this behavior by defining a job-level parameter UFT_PRINT_TEST_PARAMS as boolean and set it to false.
    [manjutest4] $ /var/lib/jenkins/workspace/manjutest4/HpToolsLauncher.exe -paramfile props04022023132832326.txt -encoding UTF-8
    /var/lib/jenkins/workspace/manjutest4/HpToolsLauncher.exe: /var/lib/jenkins/workspace/manjutest4/HpToolsLauncher.exe: cannot execute binary file
    Launch return code 126
    Build step 'Execute Micro Focus tests from file system' changed build result to FAILURE
    RunResultRecorder: no results xml File provided
    Finished: FAILURE
    --------------
    Below are the files are located under var/lib/jenkins/workspace/manjutest4/ in Linux Server.

    [root@linuxserver ~]# uname -r
    4.14.301-224.520.amzn2.x86_64
    [root@linuxserver~]# ls -ll /var/lib/jenkins/workspace/manjutest4/
    total 332
    -rwxrw-r-- 1 jenkins jenkins 262656 Feb 4 13:28 HpToolsLauncher.exe
    -rwxrw-r-- 1 jenkins jenkins 25088 Feb 4 13:28 LRAnalysisLauncher.exe
    -rwxrw-r-- 1 jenkins jenkins 2372 Feb 3 12:41 props03022023124108970.txt
    -rw-r--r-- 1 jenkins jenkins 2372 Feb 3 13:03 props03022023130359728.txt
    -rw-r--r-- 1 jenkins jenkins 2372 Feb 4 12:44 props04022023124446608.txt
    -rw-r--r-- 1 jenkins jenkins 2372 Feb 4 12:44 props04022023124448653.txt
    -rw-r--r-- 1 jenkins jenkins 2372 Feb 4 12:44 props04022023124451248.txt
    -rw-r--r-- 1 jenkins jenkins 2372 Feb 4 12:44 props04022023124455999.txt
    -rw-r--r-- 1 jenkins jenkins 2372 Feb 4 12:44 props04022023124456429.txt
    -rw-r--r-- 1 jenkins jenkins 2372 Feb 4 12:44 props04022023124457067.txt
    -rw-r--r-- 1 jenkins jenkins 2372 Feb 4 12:44 props04022023124457250.txt
    -rw-r--r-- 1 jenkins jenkins 2382 Feb 4 12:44 props04022023124458238.txt
    -rw-r--r-- 1 jenkins jenkins 2382 Feb 4 13:28 props04022023132832326.txt
    [root@linuxserver ~]#


    Thanks and regards,
    Manjunath
  • 0   in reply to Manjunath Tekkur

    Please consider all information of my first post.

    How to ask questions

    Reward contributions via likes or 'verified answers'

  • 0   in reply to Manjunath Tekkur

    Thank you for giving the reply, Now I have LRP 2022 integrated with Jenkins which is hosted in Windows Server.

    When I execute the Job (Scenario file  C:\LoadRunner\Scenario1.lrs  )I am getting following error.  Jenkins and LRP is hosted on the same Windows 2016 Server. 

    Please advise how can fix this issue?  Thanks in advance

    Running as SYSTEM Building on the built-in node in workspace C:\ProgramData\Jenkins\.jenkins\workspace\LoadRunnertest1 NOTE : The test parameters and their values are printed by default in both Console Output and Results###.xml. You can disable this behavior by defining a job-level parameter UFT_PRINT_TEST_PARAMS as boolean and set it to false. [LoadRunnertest1] $ C:\ProgramData\Jenkins\.jenkins\workspace\LoadRunnertest1\HpToolsLauncher.exe -paramfile props06022023090740114.txt -encoding UTF-8 "Started..." Run build tests Launcher timeout is 00::00:00:10 Controller Polling Interval: 30 seconds PerScenarioTimeout: 00::00:10:00 minutes FileSystemTestRunner timeout is 00:00:10 UFT Mobile connection info is - UFT Mobile HostAddress: , Port: 8080, Username: , TenantId: , UseSSL: 0, UseProxy: 0, ProxyType: 0, ProxyAddress: , ProxyPort: 0, ProxyAuth: 0, ProxyUser: Results directory is: C:\LoadRunner\Results 1 tests found: C:\LoadRunner\Scenario1.lrs ============================================================================ 06/02/2023 09:07:40 Running: C:\LoadRunner\Scenario1.lrs C:\LoadRunner\Scenario1.lrs Cleaning up the environment... Preparing scenario C:\LoadRunner\Scenario1.lrs for execution. Test result: Error uftReportDir is C:\LoadRunner\Scenario1.lrs\Report1 06/02/2023 09:07:45 Test complete: C:\LoadRunner\Scenario1.lrs ------------------------------------------------------------------------------------------------------- Error: Cannot close Controller gracefully, exception details: Error: The remote procedure call failed. (Exception from HRESULT: 0x800706BE) Error: at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData) at HP.LoadRunner.Interop.Wlrun.LrEngineClass.CloseController() at HpToolsLauncher.TestRunners.PerformanceTestRunner.closeController() Error: killing Controller process Cleaning up the environment... wlrun killed Cleaning up the environment... ================================================ Run status: Job failed, total tests: 1, succeeded: 0, failures: 0, errors: 1, warnings: 0 Error : C:\LoadRunner\Scenario1.lrs[1] ================================================ Build step 'Execute Micro Focus tests from file system' changed build result to FAILURE
    Recording test results [Checks API] No suitable checks publisher found. Report archiving mode is set to: PUBLISH_HTML_REPORT Node name = Finished: FAILURE
    Thanks na dregrads,
    Manjunath 

  • 0   in reply to Manjunath Tekkur

    Hi  , good to see that you made some progress, but unfortunate without reaching the final goal.

    I assume that you can run your test Scenario1.lrs in Controller by hand without any issues. Unfortunate I do not have any experience with using LRP in this configuration, so I can only give tips to troubleshoot based on the log info and a little general knowledge. Things you can consider:

    1. Jenkins job is running under SYSTEM account: can you experiment and use an account that you also used with running Controller stand alone?

    2. Did you scan your system to any log files that are created by LRP? (Check also Event Viewer)

    3. Can you improve Controller settings of your test: E.g. Location of default Result dir, auto save results etc. (See Controller, Results menu).

    4. Not sure, but the first error seems to be 'Test result: Error uft'. Is that related to Mobile testing?

    5. Test first with a very simple LR C script that just calls lr_message("Hallo World") and see if that completes fine via Controller  and Jenkins.

    6. There is a help page on UTF mobile and Jenkins testing.

    Success, Erik

    How to ask questions

    Reward contributions via likes or 'verified answers'