-
Bug
-
Resolution: Unresolved
-
Critical
-
Jenkins version: 2.190.3
Microfocus Application Automation Tools v5.9
Jenkins slave: Windows 10; Jenkins Master: Linux
Build-step: Execute Micro Focus tests from file system
We are using a windows slave in order to execute LoadRunner Jenkins jobs. Those jobs do not depends on each other. However jobs that started before the other and last longer preventing later jobs to be published and finished. The later jobs are waiting on queue and issue message in their console that they are waiting to the earlier job. I.e. "Publish Micro Focus tests result is waiting for a checkpoint on LR_AFF #42" (LR_AFF - is our LoadRunner Jenkins job name). In some cases we are coming and because that the earlier job stack the other jobs waits for days (during weekend). Please fix it.
[JENKINS-60514] Message: "Publish Micro Focus tests result is waiting for a checkpoint on LR_AFF #42"
Yaniv Katz
created issue -
Yaniv Katz
made changes -
| Environment | Original: hp plug-in ver. 5.9 |
New:
Jenkins version: 2.190.3 Microfocus Application Automation Tools v5.9 Jenkins slave: Windows 10; Jenkins Master: Linux Build-step: Execute Micro Focus tests from file system |
| Assignee | Original: Maria Narcisa Galan [ narcisamgalan ] | New: Rolando-Mihai Vlad [ rolandomihaivlad ] |
Yaniv Katz
added a comment - Hi Rolando,
Its not a case of running in the same slave machine. Each LR instance has a depreciated slave.
We can make webex tomorrow at 11:00. Is it suitable for you?
Thanks,
Yaniv
Yaniv Katz
added a comment - Hi Rolando,
Its not a case of running in the same slave machine. Each LR instance has a depreciated slave.
We can make webex tomorrow at 11:00. Is it suitable for you?
Thanks,
Yaniv Yaniv Katz
added a comment - GMT + 2 
Rolando-Mihai Vlad
added a comment - Sure Rolando-Mihai Vlad
added a comment - I managed to reproduce the issue. The reason "Publish Micro Focus tests results" is waiting is due to the following line: https://github.com/jenkinsci/hpe-application-automation-tools-plugin/blob/latest/src/main/java/com/microfocus/application/automation/tools/results/RunResultRecorder.java#L1455. However, changing the mode causes other issues, thus the current workflow was intended. I continue to investigate if it is possible to change the mode.
Rolando-Mihai Vlad
added a comment - I managed to reproduce the issue. The reason "Publish Micro Focus tests results" is waiting is due to the following line: https://github.com/jenkinsci/hpe-application-automation-tools-plugin/blob/latest/src/main/java/com/microfocus/application/automation/tools/results/RunResultRecorder.java#L1455 . However, changing the mode causes other issues, thus the current workflow was intended. I continue to investigate if it is possible to change the mode. Rolando-Mihai Vlad
added a comment - Hello Yaniv Katz,
I apologise for the delayed response due to holidays. I performed some code changes and you will find the modified .hpi at: https://ci.appveyor.com/project/HPEbot/hp-application-automation-tools-plugin/builds/30019176/artifacts.
Please let me know if you encounter any issues.
Regards,
Rolando
Rolando-Mihai Vlad
added a comment - Hello Yaniv Katz,
I apologise for the delayed response due to holidays. I performed some code changes and you will find the modified .hpi at: https://ci.appveyor.com/project/HPEbot/hp-application-automation-tools-plugin/builds/30019176/artifacts.
Please let me know if you encounter any issues.
Regards,
Rolando Yaniv Katz
added a comment - Hello Rolando,
Thanks! However I'm not expert to Jenkins (use sys admin). Does it contains the new version 6.0?
Regards, Yaniv
Yaniv Katz
added a comment - Hello Rolando,
Thanks! However I'm not expert to Jenkins (use sys admin). Does it contains the new version 6.0?
Regards, Yaniv 
Hello Yaniv Katz,
I am unable to reproduce your issue and I would like to see the configurations. Is it possible to schedule a webex (my working hours are 9am-5pm GMT+2) until end of week, since I will be away due to holidays after?
Please note, concurrent builds when using LoadRunner will cause issues since there can be only one instance of controller per machine.
Regards,
Rolando