Parallel builds in tinderd

[Joe Marcus Clarke]

On Sun, 2006-12-17 at 23:17 +0000, Tim Bishop wrote:
> My tinderbox machine is a dual core box, so I figured there'd be
> some benefit to being able to do multiple compiles in parallel using
> tinderd. I looked at the -jobs flag to tinderbuild, but it doesn't
> seem to do anything useful (in fact, it breaks the build).

Any updates on this?  I'd like to see the errors that this causes in the
build so that I can try and fix them.

> 
> So what I've done is hack tinderd so multiple instances can be run
> at once. Obviously only one tinderbuild can be run per build, so
> I've done some very crude locking to make sure the tinderds don't
> collide. There's plenty of scope for race conditions here :-)
> 
> The biggest benefit comes when testing a single port across multiple
> build environments. It doesn't help in the slightest when doing
> lots of ports in one build.
> 
> I've also tweaked the tinder.sh startup script to be able to start
> a given number of tinderd instances.
> 
> Unless the race conditions become a reality I probably won't fix
> them, but I'm more than happy if a more experienced shell hacker
> wants to take on that little challenge ;-)

What about my previous locking question in tinderbuild?  Is tinderd
locking still required?

Joe

> 
> Patch attached.
> 
> Tim.
> 
> _______________________________________________
> tinderbox-list at marcuscom.com mailing list
> http://marcuscom.com/mailman/listinfo/tinderbox-list
> To unsubscribe, send any mail to "tinderbox-list-unsubscribe at marcuscom.com"
-- 
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://marcuscom.com/pipermail/tinderbox-list/attachments/20061230/3c5e70de/attachment.bin