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.
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 restartin 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.
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 may appear.