|
(Note: Assigned to 'core' component only because I don't know correct component)
I'm seeing the same behavior described in JENKINS-19994 but I'm using SVN.
Our environment:
Master: Jenkins 1.509.1 running on Debian 6.0
Our slave: Win2003 64-bit
The slave VM does auto-login and has a startup script that executes;
"C:\Program Files\Java\jre6\bin\javaws.exe" http://OurJenkins/computer/OurSlave/slave-agent.jnlp"
This works fine.
Sometimes, there is an error during SVN checkout like;
— begin console —
Deleting project workspace...
done
Cleaning local Directory ./OurProj
Checking out http://OurSvn/OurRepo/trunk/OurProj at revision '2014-01-12T18:53:11.137 -0800'
A OurProj
<snip>
ERROR: Failed to check out http://OurSvn/OurRepo/trunk/OurProj/SomeDir
org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /OurRepo/!svn/vcc/default failed
— end console —
After the above checkout failure, subsequent job runs are failing immediately.
— begin console —
Deleting project workspace...
Cannot delete workspace: java.io.IOException: Unable to delete C:\opt\hudson\workspace\OurJob\SomeDir\MKL\em64t\lib\.svn\tmp\text-base\mkl_core.lib.svn-base
ERROR: Cannot delete workspace: java.io.IOException: Unable to delete C:\opt\hudson\workspace\OurJob\SomeDir\MKL\em64t\lib\.svn\tmp\text-base\mkl_core.lib.svn-base
— end console —
This will happen as many times as you want to press the 'build' button... ![]()
After several occurrences of this error, *** I manually deleted the entire $WORKSPACE directory ***. However, the problem still occurs.
After reading JENKINS-19994, I started up ProcessExplorer and did 'Find|Find Handle or DLL...' and searched for 'mkl_core'. Sure enough there was a 'javaws.exe' process found. Killing that process (by clicking the 'X' in 'Jenkins slave agent' window) and restarting the Jenkins client resolves the issue.
My understanding is that Windows will not delete (or say it deleted) a file if that file is in use. It will always complain until the file is released. This suggests to me that the javaws.exe process is reporting a false positive saying it is using a file when this is not actually the case.
So, I don't think this is a Git specific issue as described in JENKINS-19994, but rather a more widely reaching issue. (Unless there is copy-and-paste code between SVN and Git modules).
We seem to get SVN checkout errors fairly frequently (which may be a different issue either in Jenkins or our environment) so being able to avoid the "one problem means you're forever stuck" would be nice.
|
