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

Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Labels:
    • Environment:
      Windows 7 / Windows 10
      Jenkins LTS 2.164.1
      Micro Focus Application Automation Tools version 5.7 (issue does not occur in 5.6.2 or 5.5)
      UFT version 14.03 / 14.50 / 14.51
      ALM 12.55
    • Similar Issues:

      Description

      We are using the Micro Focus plugin to run a single UFT test in an ALM test set. This worked fine in previous versions of the plugin, but not in version 5.7.

      A popup on the agent (WerFault.exe, child of HpToolsLauncher.exe) shows:

      HpToolsLauncher has stopped working

       

      A problem caused the program to stop working correctly.

      Please close the program.

      [ -> Close the program]

      The Jenkins build log shows:

      Building remotely on Interactive in workspace C:\Jenkins\Agents\Interactive\workspace\ALM Test
      [ALM Test] $ "C:\Jenkins\Agents\Interactive\workspace\ALM Test\HpToolsLauncher.exe" -paramfile props17032019164142557.txt
      "Started..."
      Timeout is set to: -1
      Run mode is set to: RUN_LOCAL

      Unhandled Exception: System.ArgumentOutOfRangeException: Length cannot be less than zero.
      Parameter name: length
      {{ at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)}}
      {{ at HpToolsLauncher.AlmTestSetsRunner.Run()}}
      {{ at HpToolsLauncher.Launcher.RunTests(IAssetRunner runner, String resultsFile)}}
      {{ at HpToolsLauncher.Launcher.Run()}}
      {{ at HpToolsLauncher.Program.Main(String[] args)}}
      Finished: SUCCESS

      The final line (Finished: SUCCESS) is only shown after closing the popup.

      Aborting the test instead of closing the popup works:

      Building remotely on Interactive in workspace C:\Jenkins\Agents\Interactive\workspace\ALM Test
      [ALM Test] $ "C:\Jenkins\Agents\Interactive\workspace\ALM Test\HpToolsLauncher.exe" -paramfile props22032019185836817.txt
      "Started..."
      Timeout is set to: -1
      Run mode is set to: RUN_LOCAL

      Unhandled Exception: System.ArgumentOutOfRangeException: Length cannot be less than zero.
      Parameter name: length
      {{ at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)}}
      {{ at HpToolsLauncher.AlmTestSetsRunner.Run()}}
      {{ at HpToolsLauncher.Launcher.RunTests(IAssetRunner runner, String resultsFile)}}
      {{ at HpToolsLauncher.Launcher.Run()}}
      {{ at HpToolsLauncher.Program.Main(String[] args)}}
      [ALM Test] $ "C:\Jenkins\Agents\Interactive\workspace\ALM Test\HpToolsAborter.exe" props22032019185836817.txt
      ============================================================================
      Aborting testing tool related processes
      Trying to terminate UFTRemoteAgent...Terminated
      Operation was aborted by user.
      Build step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to ABORTED
      Finished: ABORTED

      I've also tried the following:

      • Running with a timeout (the timeout is displayed in output instead of -1, but still crashes. Presumably the timeout only applies when it runs the test.)
      • Specify a test set instead of a single test instance (no change - still crashes)

      When we downgrade the plugin to version 5.6.2 the job successfully runs the test.

        Attachments

          Activity

          Hide
          jmyates86 Joshua Yates added a comment -

          We are also seeing this issue, I have seen this occur with 2 other users at different companies with different ALM servers and versions, it does not seem to be isolated.  All of my customers using the latest 5.7 release of the application automation tools plugin had to roll back

          Tags:  Jim Sears 

          Show
          jmyates86 Joshua Yates added a comment - We are also seeing this issue, I have seen this occur with 2 other users at different companies with different ALM servers and versions, it does not seem to be isolated.  All of my customers using the latest 5.7 release of the application automation tools plugin had to roll back Tags:  Jim Sears  
          Hide
          jimsears Jim Sears added a comment -

          I can confirm Joshua's comment. Our company has had to roll back to 5.6.2 so we can continue to test.

          Jim

          Show
          jimsears Jim Sears added a comment - I can confirm Joshua's comment. Our company has had to roll back to 5.6.2 so we can continue to test. Jim
          Hide
          jklintholm Johan Klintholm added a comment -

          I have had similar experiences. What I can also see is that it affects only test set paths containing spaces.

          If I change name of a test set so that the entire path is void of spaces, the plugin actually works.

          Seems to be a really simple case of regression here.

          Show
          jklintholm Johan Klintholm added a comment - I have had similar experiences. What I can also see is that it affects only test set paths containing spaces . If I change name of a test set so that the entire path is void of spaces, the plugin actually works. Seems to be a really simple case of regression here.
          Hide
          aslaakso Anda Sorina Laakso added a comment -

          These is indeed a bug for the case when the path contains spaces. It has been fixed already, but  the fix will be available only in 5.8.

           

          Show
          aslaakso Anda Sorina Laakso added a comment - These is indeed a bug for the case when the path contains spaces. It has been fixed already, but  the fix will be available only in 5.8.  
          Hide
          zekiyureti Zeki Yureti added a comment - - edited

          I've done some more testing, and found that 5.7 works ok when running an ALM Test Set without spaces, but not an ALM Test Instance without spaces.

          When running a test instance, it gives the error "Specified test not found on ALM, please check your test path".

          I used the path:

          Root\Tests\MFJenkins\[1]InstantPass

          That works with plugin version 5.6.2, but with version 5.7 gives the following (also, the output does not use usual ALM terminology like Test Set / Instance / Folder)

          "Started..."
          Timeout is set to: -1
          Run mode is set to: RUN_LOCAL
          testName: [1]InstantPass
          testSuiteName: MFJenkins
          tsPath: Root\Tests
          ============================================================================
          Starting test set execution
          Test set name: MFJenkins, Test set id: 4901
          Number of tests in set: 0
          Error: Specified test not found on ALM, please check your test path.
          ================================================
          Run status: Job failed, total tests: 0, succeeded: 0, failures: 0, errors: 0
          ================================================
          Build step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to FAILURE
          [BFA] Scanning build for known causes...
          [BFA] No failure causes found
          [BFA] Done. 0s
          Finished: FAILURE
          Show
          zekiyureti Zeki Yureti added a comment - - edited I've done some more testing, and found that 5.7 works ok when running an ALM Test Set without spaces, but not an ALM Test Instance without spaces. When running a test instance, it gives the error "Specified test not found on ALM, please check your test path". I used the path: Root\Tests\MFJenkins\[1]InstantPass That works with plugin version 5.6.2, but with version 5.7 gives the following (also, the output does not use usual ALM terminology like Test Set / Instance / Folder) "Started..." Timeout is set to: -1 Run mode is set to: RUN_LOCAL testName: [1]InstantPass testSuiteName: MFJenkins tsPath: Root\Tests ============================================================================ Starting test set execution Test set name: MFJenkins, Test set id: 4901 Number of tests in set: 0 Error: Specified test not found on ALM, please check your test path. ================================================ Run status: Job failed, total tests: 0, succeeded: 0, failures: 0, errors: 0 ================================================ Build step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to FAILURE [BFA] Scanning build for known causes... [BFA] No failure causes found [BFA] Done. 0s Finished: FAILURE

            People

            • Assignee:
              aslaakso Anda Sorina Laakso
              Reporter:
              zekiyureti Zeki Yureti
            • Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: