-
Bug
-
Resolution: Cannot Reproduce
-
Minor
-
None
If the Jenkins job is aborted, or times out, the Unity process doesn't actually die/kill, just hangs there.
Very evident with distributed slave setup on OSX.
If the Jenkins job is aborted, or times out, the Unity process doesn't actually die/kill, just hangs there.
Very evident with distributed slave setup on OSX.
I tried to reproduce the problem in a Jenkins 1.610 distributed setup with a Linux master and a Mac slave on a 5 min Unity3d 5.0.1f1 job (I use a PostprocessBuildPlayer that sleeps for 5 min). The UNity3d plugin was v0.8.
To try to reproduce the problem, I used
In all cases, the job stopped and there was no dangling Unity3d processes on the slave.
So I am unable to reproduce this issue. Please provide more information about your environment. In particular, jenkins version, unity3d plugin version, java version, Unity3d version, etc.