-
Bug
-
Resolution: Fixed
-
Critical
-
Jenkins 2.138
HPE Application Automation Tools 5.4
Jenkins Slave (Windows server 2012 R2, HP ALM 12.53 Patch 2, HP UFT 14.03 Patch 1, Java 1.8.0_181)
Below is a snippet from the console log of the job:
29/11/2017 12:42:05 Running: [3]Driver
29/11/2017 12:42:05 Running test: [3]Driver, Test id: 1495, Test instance id: 2779
Test: [3]Driver, Id: 2779, Execution status: Running
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at HpToolsLauncher.AlmTestSetsRunner.UpdateTestStatus(TestSuiteRunResults runResults, ITestSet targetTestSet, TestExecStatus testExecStatusObj, Boolean onlyUpdateState)
at HpToolsLauncher.AlmTestSetsRunner.RunTestSet(String tsFolderName, String tsName, Double timeout, QcRunMode runMode, String runHost)
at HpToolsLauncher.AlmTestSetsRunner.Run()
at HpToolsLauncher.Launcher.RunTests(IAssetRunner runner, String resultsFile)
at HpToolsLauncher.Launcher.Run()
at HpToolsLauncher.Program.Main(String[] args)
This happens when executing a Test Set of automated Test Scripts (using UFT on Jenkins Slave). It runs through the first two test cases perfectly fine but always fails at the same spot at the beginning of Test Case 3 ([3] Driver). **Update - It does not always happen at the same spot/place but it does happen in close proximity**.
Note: The automation will continue to run on the Jenkins Slave machine and it will update the results back to ALM, however, the Jenkins job/build itself becomes stuck and it never finishes until I manually abort it even though the Test Cases have long been finished.
Screenshots of the Windows Event log Errors are attached
Also see the attached Crash details/log
Similar to bug: JENKINS-30328