The tests now seem to be running OK. There are some failures due to image comparison mismatch, but I think we should attempt to track these down as a team -- hopefully running on more computers than just mine and with James' input. To see the latest test results, click on the "stdio" link for each run of the "test" box in the waterfall display http://mpl-buildbot.code.astraw.com/waterfall .
It would be nice if the buildbot web GUI would easily let us see, for failed image-based tests, the baseline, output, and difference image, but that's not implemented (as far as I know). It would probably be possible to add something like this to the MplNosePlugin to do this with relatively little pain, although the display would be easiest via a pastebin or something rather than hooking back into a patched buildbot framework that supported test images. John Hunter wrote: > On Wed, May 20, 2009 at 3:48 AM, Andrew Straw <straw...@astraw.com> wrote: > >> Let's see if we can get all the tests passing and if this buildbot >> approach looks sustainable -- if so, I'd like to get some more build >> slaves into the mix and make MPL a good continuous integration citizen. >> I don't think the buildbot master will take many resources on my server, > > The sage project has given us access to a network accessible > persistent OSX box, so I will try and get that setup with the buildbot > infrastructure. I'm not yet familiar with the buildbot project or > approach, so I have some learning to do, so if you have a cheatsheet > or docs thaty you think are particularly handy, send them along > (otherwise I'll just make my way through the site docs) OK, here's what you do:: # (Make a username you want to run this buildslave as. # Become that user. Change into a new directory e.g. $HOME/builbot) curl http://astraw.com/mpl/bootstrap-py.txt > bootstrap.py curl http://astraw.com/mpl/buildout-example.cfg > buildout.cfg # Edit buildout.cfg according the instructions in the file. Send me # the values you added. # python bootstrap.py # bin/buildout Once you've been added to the build master: # bin/<slave-identifier-string> start And that should be it. For now we can start/stop builds by clicking the "force build" button in the buildmaster web GUI. SVN polling doesn't seem to be working yet... I'll look into that when I have time. Ditto for building binaries and uploading them somewhere. -Andrew ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
