Jenkins is probably trying to delete a file which Windows still has in use.  
Windows probably has it in use because the "devenv" script started another 
program, the devenv script died, Jenkins thought the process had died, and 
Jenkins assumed it was time to cleanup after the job.
 
I thought it was recommended not to use "devenv" for command line builds in 
Visual Studio (at least in older versions of Studio) for precisely this 
reason.  I thought the devenv script started the IDE, then the devenv script 
exited, even though the IDE continued to run.
 
Mark Waite


>________________________________
> From: Neil Bird <n...@fnxweb.com>
>To: jenkinsci-users@googlegroups.com 
>Sent: Tuesday, March 13, 2012 8:07 AM
>Subject: Jenkins thinks job has died, but devenv still compiling?
>  
>
>  The subject is a bit of a mis-nomer as the Jenkins *job* plainly has died, 
>but with a bizarre error, however the (VS2005) compilation is progressing 
>without failure in the background (but Jenkins is now unaware of it).
>
>  This is the relevant snippet of the job output:
>
><snip compilation>
>ErrorWnd.cpp
>HCIScriptReader.cpp
>ImageFactory.cpp
>FATAL: Unable to delete script file 
>C:\WINDOWS\TEMP\hudson7779321505251083067.bat
>hudson.util.IOException2: remote file operation failed: 
>C:\WINDOWS\TEMP\hudson7779321505251083067.bat at 
>hudson.remoting.Channel@17e6f05:crawd475108-xp2
>    at hudson.FilePath.act(FilePath.java:784)
>    at hudson.FilePath.act(FilePath.java:770)
>    at hudson.FilePath.delete(FilePath.java:1075)
><snip pages of callstacks>
>...
>java.io.IOException: Unexpected termination of the channel
>...
>
>
>  The job seems to have dies with an odd batch file deletion error (the file 
>no longer existed when we went to check) mid-way through the build.
>
>  Any ideas what could cause that?
>
>
>
>  What might be relevant is that this is 32-bit Windows XP SP3 inside a 
>VitualBox VM (hosted on a 64-bit many-GB Windows XP SP3 box).  We're 
>experimenting with a super-powerful build box running sep. VMs to act as 
>Jenkins slaves (e.g,. some 32-bit, some Linux, etc.)
>
>-- [neil@fnx ~]# rm -f .signature
>[neil@fnx ~]# ls -l .signature
>ls: .signature: No such file or directory
>[neil@fnx ~]# exit
>
>
>   

Reply via email to