On 29 Oct, 11:41 pm, jnol...@gmail.com wrote:
On Thu, Oct 29, 2009 at 7:04 PM, <exar...@twistedmatrix.com> wrote:
On 02:30 pm, solip...@pitrou.net wrote:
Hello,
What do you think of creating a "buildbot" category in the tracker?
There
are
often problems on specific buildbots which would be nice to track,
but
there's
nowhere to do so.
Is your idea that this would be for tracking issues with the *bots*
themselves? That is, not just for tracking cases where some test
method
fails on a particular bot, but for tracking cases where, say, a bot's
host
has run out of disk space and cannot run the tests at all?
For the case where a test is failing because of some platform or
environment
issue, it seems more sensible to track the ticket as relating to that
platform or environment, or track it in relation to the feature it
affects.
Of course, tickets could move between these classifications as
investigation
reveals new information about the problem.
Then again, I know for a fact certain tests fail ONLY on certain
buildbots because of the way they're configured. For example, certain
multiprocessing tests will fail if /dev/shm isn't accessible on Linux,
and several of the buildbosts are in tight chroot jails and don't have
that exposed.
Is it a bug in that buildbot, a platform specific bug, etc?
It's a platform configuration that can exist. If you're rejecting that
configuration and saying that CPython will not support it, then it's
silly to have a buildbot set up that way, and presumably that should be
changed.
The point is that this isn't about buildbot. It's about CPython and
what platforms it supports. Categorizing it by "buildbot" is not
useful, because no one is going to be cruising along looking for
multiprocessing issues to fix by browsing tickets by the "buildbot"
category.
If, on the other hand, (sticking with this example) /dev/shm-less
systems are not a platform that CPython wants to support, then having a
buildbot running on one is a bit silly. It will probably always fail,
and all it does is contribute another column of red. Who does that
help?
Jean-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
