[JIRA] [unity3d-plugin] (JENKINS-23958) Pipe Broken

Tue, 14 Apr 2015 10:29:27 -0700

ben s commented on Bug JENKINS-23958

Unfortunately I don't have any specific way to reproduce it. Most of our jobs are rather long, however. In fact when a job undergoes a fresh import into a new workspace, the likelihood of this error occurring seems to increase. The larger the project (the more assets) the more frequent.

It often happens after Unity lists "Used Assets, sorted by uncompressed size:"

 0.0 kb	 0.0% Assets/Resources/path/to/some/file1
 0.0 kb	 0.0% Assets/Resources/path/to/some/file2
Failure on remote 
java.io.IOException: Pipe broken
	at java.io.PipedInputStream.read(PipedInputStream.java:322)
	at java.io.PipedInputStream.read(PipedInputStream.java:378)
	at java.io.InputStream.read(InputStream.java:101)
	at org.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64)


But it also occurs in other points in time:





Unloading 0 unused Assets to reduce memory usage. Loaded Objects now: 488.
Total: 1.677543 ms (FindLiveObjects: 0.061794 ms CreateObjectMapping: 0.023056 ms MarkObjects: 1.508662 ms  DeleteObjects: 0.005961 ms)

Failure on remote 
java.io.IOException: Pipe broken
	at java.io.PipedInputStream.read(PipedInputStream.java:322)
	at java.io.PipedInputStream.read(PipedInputStream.java:378)
	at java.io.InputStream.read(InputStream.java:101)
	at org.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64)





And: 




DisplayProgressbar: Android build
DisplayProgressbar: Fetching assembly references
DisplayProgressbar: Creating staging area
DisplayProgressbar: Rebuilding resources
DisplayProgressbar: Compiling resources
DisplayProgressbar: Creating streaming package
DisplayProgressbar: Creating asset package
DisplayProgressbar: Creating APK package
Failure on remote 
java.io.IOException: Pipe broken
	at java.io.PipedInputStream.read(PipedInputStream.java:322)
	at java.io.PipedInputStream.read(PipedInputStream.java:378)
	at java.io.InputStream.read(InputStream.java:101)
	at org.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64)





All of the above are taken from completely separate projects.



And yes, all of our jobs use the -logFile option




-batchmode -quit -logFile "$WORKSPACE/unity.log" -projectPath $WORKSPACE -executeMethod Foo.bar





I've never seen the error occur more than once per build, and it never seems to cause the build to fail, but if something else causes the build to fail it can be a serious red herring. After the "pipe broken" error, the Jenkins log picks up with the next immediate build step.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to