[JIRA] (JENKINS-59718) ALM plugin when upgraded to v5.9 getting ERROR: Build step failed with exception java.lang.NullPointerException
Title: Message Title Sanjeeth Nayak created an issue Jenkins / JENKINS-59718 ALM plugin when upgraded to v5.9 getting ERROR: Build step failed with exception java.lang.NullPointerException Issue Type: Bug Assignee: Kevin Lee Components: microfocus-da-plugin Created: 2019-10-09 16:39 Labels: uft, alm Priority: Blocker Reporter: Sanjeeth Nayak Getting Below error: Started by user GIAdmin Running as SYSTEM Building in workspace D:\Jenkins\workspace\abc\abc\abc\abc123 ERROR: Build step failed with exception java.lang.NullPointerException at com.microfocus.application.automation.tools.model.RunFromAlmModel.CreateProperties(RunFromAlmModel.java:161) at com.microfocus.application.automation.tools.model.RunFromAlmModel.getProperties(RunFromAlmModel.java:151) at com.microfocus.application.automation.tools.run.RunFromAlmBuilder.perform(RunFromAlmBuilder.java:211) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'Execute Micro Focus functional tests from Micro Focus ALM' marked build as failure Recording test results RunResultRecorder: didn't find any test results to record Finished: FAILURE Steps to reproduce:
[JIRA] (JENKINS-59416) getting NullReferenceException still job is marked as success
Title: Message Title Sanjeeth Nayak commented on JENKINS-59416 Re: getting NullReferenceException still job is marked as success Thank you for your response... What is the probable date of release of same? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201978.1568780076000.4085.1569322440126%40Atlassian.JIRA.
[JIRA] (JENKINS-59499) Job timed out - Tests Aborted - Still tests are marked as passed
Title: Message Title Sanjeeth Nayak updated an issue Jenkins / JENKINS-59499 Job timed out - Tests Aborted - Still tests are marked as passed Change By: Sanjeeth Nayak Test runs getting aborted due to job time out issue. And result pan will mark all the not run tests as passed (Which is dangerous as we might blindly think tests have passed but it has not even attempted to run)Logs: Started by upstream project "DM_UAT_TestPipelines/Pipeline-DM_DPTBs_FAR-GER" build number 24 originally caused by: Started by timer Running as SYSTEM Building in workspace D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC [JOBFOLDER_ABC] $ D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC\HpToolsLauncher.exe -paramfile props24092019010010681.txt "Started..." Timeout is set to: 5000 Run mode is set to: RUN_REMOTE Starting test set execution Test set name: Reg_ABC, Test set id: 5103 Number of tests in set: 15 Test 1: [1]004_a_abc will run on host: ne2dhtm0111 Test 2: [1]005_a_abc will run on host: ne2dhtm0111 Test 3: [1]006_a_abc will run on host: ne2dhtm0111 Test 4: [1]007_a_abc will run on host: ne2dhtm0111 Test 5: [1]008_a_abcItinerary will run on host: ne2dhtm0111 Test 6: [1]009_a_abc will run on host: ne2dhtm0111 Test 7: [1]013_a_abc will run on host: ne2dhtm0111 Test 8: [1]017_a_abc will run on host: ne2dhtm0111 Test 9: [1]016_a_abc will run on host: ne2dhtm0111 Test 10: [1]018_a_abc will run on host: ne2dhtm0111 Test 11: [1]019_a_abc will run on host: ne2dhtm0111 Test 12: [1]010_a_abcr will run on host: ne2dhtm0111 Test 13: [1]011_a_abc will run on host: ne2dhtm0111 Test 14: [1]012_a_abc will run on host: ne2dhtm0111 Test 15: [1]014_a_abc will run on host: ne2dhtm0111 "Scheduler started at:24/09/2019 01:00:16 --- 24/09/2019 01:00:16 Running: [1]004_a_abc 24/09/2019 01:00:16 Running test: [1]004_a_abc, Test id: 547, Test instance id: 764 Test: [1]004_a_abc, Id: 764, Execution status: Running Close last test 24/09/2019 02:23:33 Test complete: [1]004_a_Acceptance --- Test: [1]004_a_abc, Status: Running, Message: Connecting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312313 Test: [1]005_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=17632 Test: [1]006_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312314 Test: [1]007_a_abc, Status:
[JIRA] (JENKINS-59499) Job timed out - Tests Aborted - Still tests are marked as passed
Title: Message Title Sanjeeth Nayak updated an issue Jenkins / JENKINS-59499 Job timed out - Tests Aborted - Still tests are marked as passed Change By: Sanjeeth Nayak Started by upstream project "DM_UAT_TestPipelines/Pipeline- DM_PDBTs_FAR DM_DPTBs_FAR -GER" build number 24 originally caused by: Started by timer Running as SYSTEM Building in workspace D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC [JOBFOLDER_ABC] $ D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC\HpToolsLauncher.exe -paramfile props24092019010010681.txt "Started..." Timeout is set to: 5000 Run mode is set to: RUN_REMOTE Starting test set execution Test set name: Reg_ABC, Test set id: 5103 Number of tests in set: 15 Test 1: [1]004_a_abc will run on host: ne2dhtm0111 Test 2: [1]005_a_abc will run on host: ne2dhtm0111 Test 3: [1]006_a_abc will run on host: ne2dhtm0111 Test 4: [1]007_a_abc will run on host: ne2dhtm0111 Test 5: [1]008_a_abcItinerary will run on host: ne2dhtm0111 Test 6: [1]009_a_abc will run on host: ne2dhtm0111 Test 7: [1]013_a_abc will run on host: ne2dhtm0111 Test 8: [1]017_a_abc will run on host: ne2dhtm0111 Test 9: [1]016_a_abc will run on host: ne2dhtm0111 Test 10: [1]018_a_abc will run on host: ne2dhtm0111 Test 11: [1]019_a_abc will run on host: ne2dhtm0111 Test 12: [1]010_a_abcr will run on host: ne2dhtm0111 Test 13: [1]011_a_abc will run on host: ne2dhtm0111 Test 14: [1]012_a_abc will run on host: ne2dhtm0111 Test 15: [1]014_a_abc will run on host: ne2dhtm0111 "Scheduler started at:24/09/2019 01:00:16 --- 24/09/2019 01:00:16 Running: [1]004_a_abc 24/09/2019 01:00:16 Running test: [1]004_a_abc, Test id: 547, Test instance id: 764 Test: [1]004_a_abc, Id: 764, Execution status: Running Close last test 24/09/2019 02:23:33 Test complete: [1]004_a_Acceptance --- Test: [1]004_a_abc, Status: Running, Message: Connecting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312313 Test: [1]005_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=17632 Test: [1]006_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312314 Test: [1]007_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312315 Test: [1]008_a_abc, Status: Waiting, Message: Waiting..., Link:
[JIRA] (JENKINS-59499) Job timed out - Tests Aborted - Still tests are marked as passed
Title: Message Title Sanjeeth Nayak updated an issue Jenkins / JENKINS-59499 Job timed out - Tests Aborted - Still tests are marked as passed Change By: Sanjeeth Nayak Started by upstream project "DM_UAT_TestPipelines/Pipeline-DM_PDBTs_FAR- REG GER " build number 24originally caused by: Started by timerRunning as SYSTEMBuilding in workspace D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC[JOBFOLDER_ABC] $ D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC\HpToolsLauncher.exe -paramfile props24092019010010681.txt"Started..."Timeout is set to: 5000Run mode is set to: RUN_REMOTEStarting test set executionTest set name: Reg_ABC, Test set id: 5103Number of tests in set: 15Test 1: [1]004_a_abc will run on host: ne2dhtm0111Test 2: [1]005_a_abc will run on host: ne2dhtm0111Test 3: [1]006_a_abc will run on host: ne2dhtm0111Test 4: [1]007_a_abc will run on host: ne2dhtm0111Test 5: [1]008_a_abcItinerary will run on host: ne2dhtm0111Test 6: [1]009_a_abc will run on host: ne2dhtm0111Test 7: [1]013_a_abc will run on host: ne2dhtm0111Test 8: [1]017_a_abc will run on host: ne2dhtm0111Test 9: [1]016_a_abc will run on host: ne2dhtm0111Test 10: [1]018_a_abc will run on host: ne2dhtm0111Test 11: [1]019_a_abc will run on host: ne2dhtm0111Test 12: [1]010_a_abcr will run on host: ne2dhtm0111Test 13: [1]011_a_abc will run on host: ne2dhtm0111Test 14: [1]012_a_abc will run on host: ne2dhtm0111Test 15: [1]014_a_abc will run on host: ne2dhtm0111"Scheduler started at:24/09/2019 01:00:16---24/09/2019 01:00:16 Running: [1]004_a_abc24/09/2019 01:00:16 Running test: [1]004_a_abc, Test id: 547, Test instance id: 764Test: [1]004_a_abc, Id: 764, Execution status: RunningClose last test24/09/2019 02:23:33 Test complete: [1]004_a_Acceptance---Test: [1]004_a_abc, Status: Running, Message: Connecting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312313Test: [1]005_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=17632Test: [1]006_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312314Test: [1]007_a_abc, Status: Waiting, Message: Waiting..., Link: td://almlink:8080/qcbin//TestRunsModule-0908123123?EntityType=IRun=12312315Test: [1]008_a_abc, Status: Waiting, Message: Waiting..., Link:
[JIRA] (JENKINS-59499) Job timed out - Tests Aborted - Still tests are marked as passed
Title: Message Title Sanjeeth Nayak created an issue Jenkins / JENKINS-59499 Job timed out - Tests Aborted - Still tests are marked as passed Issue Type: Bug Assignee: Kevin Lee Attachments: image-2019-09-24-09-38-31-434.png Components: microfocus-da-plugin Created: 2019-09-24 04:08 Environment: plugin version 5.8 Labels: uft Priority: Critical Reporter: Sanjeeth Nayak Started by upstream project "DM_UAT_TestPipelines/Pipeline-DM_PDBTs_FAR-REG" build number 24 originally caused by: Started by timer Running as SYSTEM Building in workspace D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC [JOBFOLDER_ABC] $ D:\Jenkins\workspace\DMTestsFAR\DM_PDBTs_FAR\JOBFOLDER\JOBFOLDER_ABC\HpToolsLauncher.exe -paramfile props24092019010010681.txt "Started..." Timeout is set to: 5000 Run mode is set to: RUN_REMOTE Starting test set execution Test set name: Reg_ABC, Test set id: 5103 Number of tests in set: 15 Test 1: [1]004_a_abc will run on host: ne2dhtm0111 Test 2: [1]005_a_abc will run on host: ne2dhtm0111 Test 3: [1]006_a_abc will run on host: ne2dhtm0111 Test 4: [1]007_a_abc will run on host: ne2dhtm0111 Test 5: [1]008_a_abcItinerary will run on host: ne2dhtm0111 Test 6: [1]009_a_abc will run on host:
[JIRA] (JENKINS-59416) getting NullReferenceException still job is marked as success
Title: Message Title Sanjeeth Nayak commented on JENKINS-59416 Re: getting NullReferenceException still job is marked as success Hello, v5.8 i am using. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201978.1568780076000.2600.1569211860153%40Atlassian.JIRA.
[JIRA] (JENKINS-59416) getting NullReferenceException still job is marked as success
Title: Message Title Sanjeeth Nayak created an issue Jenkins / JENKINS-59416 getting NullReferenceException still job is marked as success Issue Type: Bug Assignee: Maria Narcisa Galan Components: hp-application-automation-tools-plugin Created: 2019-09-18 04:14 Priority: Blocker Reporter: Sanjeeth Nayak 18/09/2019 00:52:33 Running: [1]002_XYZ 18/09/2019 00:52:33 Running test: [1]002_XYZ, Test id: 724, Test instance id: 1992 Test: [1]002_XYZ, Id: 1992, Execution status: Running Close last test Unhandled Exception: System.NullReferenceException: Your Quality Center session has been disconnected. Contact your system administrator for more information at Mercury.TD.Client.Ota.QC9.ITSTest.get_LastRun() at HpToolsLauncher.AlmTestSetsRunner.GetTestRunId(ITSTest currentTest) at HpToolsLauncher.AlmTestSetsRunner.WriteTestRunSummary(ITSTest prevTest) at HpToolsLauncher.AlmTestSetsRunner.RunTestSet(String tsFolderName, String tsName, String testParameters, Double timeout, QcRunMode runMode, String runHost, Boolean isFilterSelected, String filterByName, List`1 filterByStatuses) at HpToolsLauncher.AlmTestSetsRunner.Run() at HpToolsLauncher.Launcher.Run() at HpToolsLauncher.Program.Main(String[] args) Recording test results None of the test reports contained any result RunResultRecorder: didn't find any test results to record Finished: SUCCESS
