Re: Distributed builds vs. Dynamic Network & Routing
Re: Distributed builds vs. Dynamic Network & Routing
- Subject: Re: Distributed builds vs. Dynamic Network & Routing
- From: Scott Tooker <email@hidden>
- Date: Sat, 12 Feb 2005 00:38:13 -0800
On Feb 11, 2005, at 10:02 AM, Tom Harrington wrote:
I've been experimenting with distributed builds this week for the
first time, and I've noticed it seems to have trouble with my network
setup. My setup's not atypical, I think-- I work on a Powerbook and
have other Macs available for distributed builds. Oddities I've
noticed include the following. I'm interested to hear whether these
are known bugs, or if there are workarounds, or if they need a new
entry in Radar. This is all with Mac OS X 10.3.8 (Darwin 7.8.0), and
XCode 1.5.
1. Multiple routes multiply jobs
My PB and the other Macs are linked by a wired network. And also by
Airport. Result == each machine used for building shows up twice in
the XCode distributed build prefs. I then end up with twice as many
compilation jobs in progress as I have machines available for
building. I haven't worked out whether this is a net gain or loss yet
in terms of build time, but either way it seems like it shouldn't be
happening.
No it shouldn't. Please file a bug on this.
2. Inability to handle dynamic networking.
This morning I took my PB away from my desk-- unplugging the wired
network, but leaving Airport active. Soon the fan started running at
high speed. Turns out distccschedd was using >90% of CPU, and I
wasn't even using XCode at the time.
Xcode 1.5 is not mobile aware at all when it comes to distributed
builds. The next version of Xcode is much better in this regard.
3. Deadlocked builds
I haven't been able to pin down the exact circumstances, but I
sometimes notice these messages appearing repeatedly in the build log:
distcc[3873] ERROR: failed to read: Resource temporarily unavailable
distcc[3873] ERROR: read failed while waiting for token "ZCLL"
distcc[3873] ERROR: Unable to read zeroconfig service list length
distcc[3873] ERROR: Unable to use zeroconfig; can't distribute work
When this happens, I inevitably end up getting this message instead,
also repeatedly:
distcc[3880] ERROR: failed to connect to port 3633: (60) Operation
timed out
Once I reach that stage the build seems to deadlock, and whatever
files are currently in progress never complete. I can stop the build,
but this also leads to distccschedd maxing out the CPU, so it needs to
be killed as well.
If you can get a reproducible test case (small enough to attach to a
bug) that would be great.
Scott
--
Tom Harrington
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden