Btw, how does patchwatcher handle that? Does it detect that in the case of changing config.h.in, dlls/Makefile.in, server/protocol.def it needs to regenerate the files by running autoconf, tools/make_requests, or tools/make_makefiles?
Not at all.
Patches gratefully accepted.
Status: - posted note about two bugs in patch series handling, will fix tomorrow - "time baseline_tests" doesn't work (limitation of time cmd), need to fix borkage there. Sloppy. - Austin sent in a patch to install gecko - I'm close to having valgrind integration, but haven't looked at how to make it fast enough yet. - user32:monitor.c:262: Test failed: Failed to reset default resolution is happening lately; should probably restart X server between runs
On Tuesday 19 August 2008 02:36:02 Dan Kegel wrote:
Btw, how does patchwatcher handle that?
Not at all.
Patches gratefully accepted.
Whoops, I just realized this came across rather rude. Sorry for that. I'm currently trying to get the basic features of the patchwatcher to work in buildbot and know how hard this stuff is.
I'm actually glad for you pioneering in this area, allowing me to steal^Wuse ideas for integration into buildbot.
Cheers, Kai
Kai wrote:
Btw, how does patchwatcher handle that?
Not at all.
Whoops, I just realized this came across rather rude
Nah, that was fine. (Although "it doesn't yet" might have been clearer.)
I'm currently trying to get the basic features of the patchwatcher to work in buildbot and know how hard this stuff is.
I was totally jazzed when I saw you were doing that. Good luck!
I'm actually glad for you pioneering in this area, allowing me to steal^Wuse ideas for integration into buildbot.
Yeah, I hope it's a useful prototype for you. My gut feeling is that it might be a while before you catch up, but I hope I'm wrong. I'd love to see you pass me before I have to add support for distributed build slaves to patchwatcher! - Dan