On 30 January 2011 20:50, David Bolen <db3l....@gmail.com> wrote: > I haven't been able to - as you say there's no good way to hook into > the build process in real time as the changes have to be external or > they'll get zapped on the next checkout. I suppose you could rapidly > try to monitor the output of the build slave log file, but then you > risk killing a process from a next step if you miss something or are > too slow. And I've had cases (after long periods of continuous > runtime) where the build slave log stops being generated even while > the slave is running fine.
OK, sounds like I hadn't missed anything, then, which is good in some sense :-) > For now though, these two external "monitors" seem to have helped > contain the number of manual operations I have to do on my two Windows > slaves. (Though recently I've begun seeing two new sorts of pop-ups > under Windows 7 but both related to memory, so I think I just need to > give my VM a little more memory) Yes, my (somewhat more simplistic) kill scripts had done some good as well. Having said that, http://bugs.python.org/issue9931 is currently stopping my buildslave (at least if I run it as a service), so it's a bit of a moot point at the moment... (One thing that might be good is if there were a means in the buildslave architecture to deliberately disable a test temporarily, if it's known to fail - I know ignoring errors isn't a good thing in general, but OTOH, having a slave effectively dead for months because of a known issue isn't a lot of help, either :-() Thanks for the reply. Paul. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
