Am 04.08.2010 21:03, schrieb Paul Moore: > On 4 August 2010 18:42, "Martin v. Löwis" <mar...@v.loewis.de> wrote: >>> I don't really have any answer to this problem right now. Is it >>> possible to set up a local buildslave-like environment (so I can run >>> the test suite on my development PC without needing to set up access >>> and register that PC as a temporary buildslave, which wouldn't be >>> practical for me)? If I can get an environment where I can run the >>> tests as I need and debug them in place, I might be able to work on >>> improving the reliability of things. > > Sorry, I wasn't clear. The issues I see tend to look like they come > from the test suite being run under the control of the buildbot > service - issues caused by not having a terminal session or window > station (like the JIT debugger appearing, which Curt pointed out a way > of addressing) or issues relating to my seeing orphaned python_d.exe > processes which never occur for me when running the test suite > manually.
Ah. It should certainly be possible to set this up locally - you just need to run a buildbot master as well, either on the same machine or a different one. The only thing you can't then get is automatic notifications on commits. You could emulate this with manually triggering builds over the master web pages, or by using buildbot's svnpoller change source (which defaults to a poll interval of 10min). To get started, I could share with you the master configuration of python.org (with account information stripped, of course). Regards, Martin _______________________________________________ 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
