Paul Burba wrote:
> Anyway, Garrett, if you (or someone else running debian) have a moment to
> check if this patch solves the problem that would be great. Worst case,
> if no one has time for this I can commit it and let the buildbot test it.
> Normally I wouldn't do this, but I'm quite confident this patch solves the
> problem (famous last words I know).
The patch has solved the problem!
Concerning your remark about how you're using (or not using) buildbot. I
assume you're used to a continuous integration solution, where a failed
build leads to lava lamps glowing red, public humiliation or buying
croissants (er donuts?) for the whole team.
The Subversion buildbot is setup with a broader purpose:
First of all it's about continuous integration obviously: fast feedback
on build problems so people don't waste time fixing a broken build.
Expected resolution time: asap.
Second, we run all the regression tests (currently ra_local only) on the
new revision, thereby testing if that change doesn't change the behavior
svn in a negative way. Expected resolution time: a few days max.
Third, buildbot slaves are installed on multiple platforms. For now
these are Debian Sarge, Windows XP & Mac , but I hope to expand that. We
give developers access to other platforms to use at work/home. If a
platform specific issue shows up during a build step, we can't blame the
change committer for that.
So, don't hesitate to let buildbot test your patch.
In fact, the reason why buildbot was chosen, was because it has a
feature to try a patch first on one or more slaves before committing. If
you try a patch, buildbot will update to the last revision, apply your
patch, build and test it but it won't send an email to the svn-breakage
list (you can check the result on the webpage).
Currently I'm the only one using the try mechanism, but if you or other
committers are interested I can explain you how it works. Or, I can
present buildbot and the try feature on the Summit.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Aug 22 21:02:41 2006