• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: hp-application-automation-tools-plugin
• Labels:

  None
• Environment:

  Jenkins version: 2.107.3
  Microfocus Application Automation Tools v5.8
  Jenkins slave: Windows 10; Jenkins Master: Linux
  Build-step: Execute Micro Focus tests from file system

1. 

   image-2019-10-21-11-20-13-086.png

   36 kB

   2019-10-21 08:20

2. 

   image-2019-10-21-11-01-55-973.png

   28 kB

   2019-10-21 08:01

3. 

   image-2019-10-21-11-00-15-180.png

   27 kB

   2019-10-21 08:00

[JENKINS-59864] Job can stuck forever after message wlrun killed

Aliaksandr Kavaliou created issue - 2019-10-21 08:21

Aliaksandr Kavaliou made changes - 2019-10-21 08:22

Summary

Original: Job stuck forever after message wlrun killed

New: Job can stuck forever after message wlrun killed

Aliaksandr Kavaliou made changes - 2019-10-21 08:22

Description

Original: The issue appears from time to time. In console log of the job as you can see in the picture below - job is waiting for something (this time it has been waiting during 2+ days) and "wlrun killed" message exists. !image-2019-10-21-11-01-55-973.png! But in the Jenkins slave machine (Windows 10) the wlrun.exe process is alive. !image-2019-10-21-11-20-13-086.png! Jenkins runs via JNLP (java 8 jdk b201).  After restartin agent job can pass and after a while the issue sporadically can appear.

New: The issue appears from time to time. In console log of the job as you can see in the picture below - job is waiting for something (this time it has been waiting during 2+ days) and "wlrun killed" message exists. !image-2019-10-21-11-01-55-973.png! But in the Jenkins slave machine (Windows 10) the wlrun.exe process is alive. !image-2019-10-21-11-20-13-086.png! Jenkins slave runs via JNLP (java 8 jdk b201).  After restartin agent job can pass and after a while the issue sporadically can appear.

Aliaksandr Kavaliou made changes - 2019-10-21 08:24

Description

Original: The issue appears from time to time. In console log of the job as you can see in the picture below - job is waiting for something (this time it has been waiting during 2+ days) and "wlrun killed" message exists. !image-2019-10-21-11-01-55-973.png! But in the Jenkins slave machine (Windows 10) the wlrun.exe process is alive. !image-2019-10-21-11-20-13-086.png! Jenkins slave runs via JNLP (java 8 jdk b201).  After restartin agent job can pass and after a while the issue sporadically can appear.

New: The issue appears from time to time. In console log of the freestyle job as you can see in the picture below - job is waiting for something (this time it has been waiting during 2+ days) and "wlrun killed" message exists. !image-2019-10-21-11-01-55-973.png! But in the Jenkins slave machine (Windows 10) the wlrun.exe process is alive. !image-2019-10-21-11-20-13-086.png! Jenkins slave runs via JNLP (java 8 jdk b201).  After restarting agent (close the above window and run slave-agent.jnlp from cmd as Administrator) the job can pass and after a while the issue sporadically can appear.

Aliaksandr Kavaliou made changes - 2019-10-21 08:24

Description

Original: The issue appears from time to time. In console log of the freestyle job as you can see in the picture below - job is waiting for something (this time it has been waiting during 2+ days) and "wlrun killed" message exists. !image-2019-10-21-11-01-55-973.png! But in the Jenkins slave machine (Windows 10) the wlrun.exe process is alive. !image-2019-10-21-11-20-13-086.png! Jenkins slave runs via JNLP (java 8 jdk b201).  After restarting agent (close the above window and run slave-agent.jnlp from cmd as Administrator) the job can pass and after a while the issue sporadically can appear.

New: The issue appears from time to time. In console log of the freestyle job as you can see in the picture below - job is waiting for something (this time it has been waiting during 2+ days) and "wlrun killed" message exists. !image-2019-10-21-11-01-55-973.png! But in the Jenkins slave machine (Windows 10) the wlrun.exe process is alive. !image-2019-10-21-11-20-13-086.png! Jenkins slave runs via JNLP (java 8 jdk b201).  After restarting agent (close the above window and run slave-agent.jnlp from cmd as Administrator) the job can pass and after a while the issue sporadically may appear.

Maria Narcisa Galan made changes - 2019-10-21 08:47

Comment

[ Hi, Could you please install the 5.9 version of the plugin |http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/hp-application-automation-tools-plugin/5.9/hp-application-automation-tools-plugin-5.9.hpi] and latest version of Jenkins(2.138 , 2.150, 2.164, 2.176, 2.190)?  ]