Today I was running a full build of jenkins (current trunk), without the skipping of tests. This build however did not complete because of a failing test.
This is the error I'm getting from maven (only these two lines):
Tests in error: testRemoting(hudson.util.ProcessTreeTest): Failed to open process error=87 at .\envvar-cmdline.cpp:53
I also had a different error in a previous attempt, but for some reason I cannot reproduce it. Fortunately I have the error:
Tests in error: testCopyTo2(hudson.FilePathTest): remote file operation failed: C:\src\jenkins\jenkins\core\target\testCopyTo2867639487262230073 at hudson.remoting.Channel@63b0bdc8: The other side of the channel
testRemoting(hudson.util.ProcessTreeTest): Failed to open process error=87 at .\envvar-cmdline.cpp:53
I really have no clue what's causing all of this, but I'm throwing this on the mailing list because of the comment in the FilePathTest ("An attempt to reproduce the file descriptor leak."). It makes me think this is a really rare exotic bug.
What might be helping is that I'm running Windows 7 (SP1), maven 2.2.1, and 64-bit Java.
C:\src\jenkins\jenkins>java -version java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b07) Java HotSpot(TM) 64-Bit Server VM (build 17.0-b17, mixed mode)
Also, an issue existed about the FilePathTest (JENKINS-4090) but was marked as non-reproducable. An issue for the ProcessTreeTest exists (JENKINS-8614) and is still open.
Please let me know if anyone has suggestions to find out why this exactly happens.