|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi lacostej!
We are currently using Jenkins 1.574 (newest stable), and this has happened with pretty much every Jenkins version for the last couple of months.
Yes, we are using -logFile (to prevent multiple concurrent builds from overwriting the same log). Here's the argument to the Unity plugin:
-noGraphics -batchmode -quit -projectPath “/XXX/workspace/YYY/ZZZ" -logFile "/XXX/workspace/YYY/Editor.log" -executeMethod Builder.BuildFromCommandLine -CustomArgs:Mode=Debug;Target=iPhone;OutputPath=/XXX/workspace/YYY/Build/iOS_XCode
If I open the log file at /XXX/workspace/YYY/Editor.log I can see the lines following the pipe broken error (Updating Assets - GUID: 00000000000000001000000000000000... etc.), so Unity is definitely outputting that to the log. For whatever reason the Unity plugin's stream reader seems to think that the log stream gets broken there and bails out. I don't know if the stream times out or what the heck is going on there? Please let me know if you need any more info.
PS. The same error happens without -logFile as well, albeit it seemed to happen more often (could be because concurrent builds could overwrite the same log in that scenario). But even when building ONE build at a time, using -logFile or not using it can still invoke the same pipe broken error.