-
Bug
-
Resolution: Fixed
-
Critical
-
* Hudson 1.393 on FC13, Tomcat 6.0.20, x86_64, Oracle Java(TM) SE Runtime Environment (build 1.6.0_21-b06), 124Gb RAM or which 60Gb+ free, 7tb disk space, 24 cores.
* Jenkins 1.415 on FC13, Tomcat 6.0.20, x86_64, Oracle Java(TM) SE Runtime Environment (build 1.6.0_21-b06), 4gb ram, 120Gb disk, 4 cores.* Hudson 1.393 on FC13, Tomcat 6.0.20, x86_64, Oracle Java(TM) SE Runtime Environment (build 1.6.0_21-b06), 124Gb RAM or which 60Gb+ free, 7tb disk space, 24 cores. * Jenkins 1.415 on FC13, Tomcat 6.0.20, x86_64, Oracle Java(TM) SE Runtime Environment (build 1.6.0_21-b06), 4gb ram, 120Gb disk, 4 cores.
Concurrent Builds workspaces are sometimes removed before the build steps have completed.
This is not seen on the primary workspace, only those that get "@2" etc appended.
This causes a failure on the job in question - symptoms somewhat varying depending on the process running. Generally a file not found, followed by a process complaining that its Current Working directory has gone.
Hard to reproduce, but reproducibility seems to increase with uptime from rare to more than daily.
Affects builds running on both linux and windows slave nodes. Not seen on builds running on master.
Disk space, memory and cpu availability more than adequate.
- is duplicated by
-
JENKINS-10054 Build run on .../workspace@2 when option concurrent builds checked
- Resolved
- is related to
-
JENKINS-9950 ERROR: Failed to clean the workspace
- Resolved
-
JENKINS-7827 Workspace cleared randomly causing jobs to fail
- Resolved