Martin v. Löwis mar...@v.loewis.de added the comment:
I'm closing this as won't fix. If there is a need to run specific tests in
specific ways, it is best to check in code that does it as desired. If it is
then unacceptable to run that change on all slaves, a branch can be created,
and
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
priority: - normal
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2611
___
Neal Norwitz [EMAIL PROTECTED] added the comment:
I think this will be fairly difficult to set up. If the clean buildstep
had been executed, you would have to rerun configure and compile before
you can run any tests.
We could re-order and do clean first. That would leave all the build
Martin v. Löwis [EMAIL PROTECTED] added the comment:
We could re-order and do clean first. That would leave all the build
artifacts in tact after a build which would be nice for some
debugging.
With the current setup, that wouldn't quite work. We can't run it before
configure, because we
New submission from Trent Nelson [EMAIL PROTECTED]:
It'd be nice if there was a facility to force a particular test to be
re-run in verbose mode with the most recent build via the buildbot web
interface. It would allow us to get a bit more information about
what's going on when the buildbots
