[JIRA] (JENKINS-56676) Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException
Title: Message Title
Zeki Yureti edited a comment on JENKINS-56676
Re: Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException
I've done some more testing, and found that 5.7 works ok (runs, but does not find all test instances in the test set) 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:{noformat}Root\Tests\MFJenkins\[1]InstantPass{noformat}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) {noformat}"Started..."Timeout is set to: -1Run mode is set to: RUN_LOCALtestName: [1]InstantPasstestSuiteName: MFJenkinstsPath: Root\TestsStarting test set executionTest set name: MFJenkins, Test set id: 4901Number of tests in set: 0Error: Specified test not found on ALM, please check your test path.Run status: Job failed, total tests: 0, succeeded: 0, failures: 0, errors: 0Build 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. 0sFinished: FAILURE{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56676) Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException
Title: Message Title Zeki Yureti commented on JENKINS-56676 Re: Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException I've done some more testing, and found that 5.7 works ok (runs, but does not find all test instances in the test set) 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 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56676) Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException
Title: Message Title Zeki Yureti created an issue Jenkins / JENKINS-56676 Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException Issue Type: Bug Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2019-03-22 09:15 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 Priority: Critical Reporter: Zeki Yureti 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:
[JIRA] (JENKINS-56542) Build Token Root delays 1000 times longer than expected
Title: Message Title Zeki Yureti created an issue Jenkins / JENKINS-56542 Build Token Root delays 1000 times longer than expected Issue Type: Bug Assignee: Unassigned Components: build-token-root-plugin Created: 2019-03-13 13:15 Environment: Jenkins LTS 2.150.3 Lots of plugins including Build Token Root Plugin (version 1.4) Windows Server 2016 / Windows 10 Priority: Minor Reporter: Zeki Yureti We are using the Build Token Root Plugin (version 1.4) to trigger builds with a HTTP GET request, and have noticed that when we pass a delay parameter, the actual delay (shown in the build queue) is significantly longer than requested. http://server:8080/buildByToken/buildWithParameters?job=ajobname=thetoken=value=900sec delay=900sec => 10 days delay=30sec => 8 hr delay=1sec => 16 min It looks like those were 1000 times longer than they should have been. 90 seconds = 10.4 days 3 seconds = 8.3 hours 1000 seconds = 16.6 mins My guess is that this is related to JENKINS-44052 (passing a value in milliseconds to a function expecting seconds)
