I brought up the proof-of-concept buildbot-based patchwatcher on two old PCs here; its status page is http://buildbot.kegel.com/ It has caught one real problem so far this morning.
to-do list: - make cleaner script and doc for adding a new slave - make it start automatically after reboot - sandbox it - turn on build result emails - add a bit of parallelism into the test runner, so e.g. tests that don't need the display or network run in parallel with those that do, probably in a separate wineprefix - add valgrind slave - add windows slave (like testbot, but with real graphics and sound) - add x86_64 slave - move master to winehq.org once it seems ready
Here are the tests I had to blacklist so far:
# http://bugs.winehq.org/show_bug.cgi?id=12053 touch dlls/user32/tests/msg.ok touch dlls/user32/tests/win.ok touch dlls/user32/tests/input.ok # http://bugs.winehq.org/show_bug.cgi?id=28038 touch dlls/wininet/tests/urlcache.ok # http://bugs.winehq.org/show_bug.cgi?id=28109 touch dlls/winmm/tests/capture.ok # http://bugs.winehq.org/show_bug.cgi?id=28048 touch dlls/winmm/tests/wave.ok # Blacklist until http://www.winehq.org/pipermail/wine-patches/2011-August/105358.html in touch dlls/winhttp/tests/winhttp.ok # http://bugs.winehq.org/show_bug.cgi?id=28102 touch dlls/ws2_32/tests/sock.ok # http://bugs.winehq.org/show_bug.cgi?id=28108 touch dlls/urlmon/tests/url.ok
-
Dan Kegel