On Sun, 2013-09-29 14:03:43 +0200, Jan-Benedict Glaw <jbg...@lug-owl.de> wrote: > Just to mention: I integrated a first machine, gcc76, into my build > robot. Since yesterday, it started to build jobs > (http://toolchain.lug-owl.de/buildbot/). This box is used as a > playground for my next-generation build script, which I hope to write > as flexible and portable as needed to deploy it on a wide variety of > different platforms.
Right now, I think I addressed all bugs I was aware of. `gcc76' is
now a fully functional builder, you can see it's results here:
http://toolchain.lug-owl.de/buildbot/
http://toolchain.lug-owl.de/buildbot/timeline.php
I'll want to rework the scheduling scheme, though. Right now, it works
like this: One thread polls the relevant GIT repos for upstream
changes (every 15min.) If something new is detected, all threads (one
for each builder) are signaled that there's something new.
Each of these threads will (upon something new committed) finish its
currently running build. It'll also check if, based on the last
builds, more builds would finish in-time before the _last_ thread
would finish its current build.
That means that I'll waste time waiting for all threads to finish
before starting a new round. That could be optimized, though it's not
really _wrong_ doing so.
MfG, JBG
--
Jan-Benedict Glaw jbg...@lug-owl.de +49-172-7608481
Signature of: Gib Dein Bestes. Dann übertriff Dich selbst!
the second :
signature.asc
Description: Digital signature
_______________________________________________ Gcc-cfarm-users mailing list Gcc-cfarm-users@gna.org https://mail.gna.org/listinfo/gcc-cfarm-users
