This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients r.david.murray, zach.ware
Date 2015-07-29.21:37:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1438205868.81.0.648770198589.issue24751@psf.upfronthosting.co.za>
In-reply-to
Content
I think option 1 is to be preferred.  One of the things we've been talking about for the workflow is gating on the buildbots passing, and the way that works with flaky tests is if the check fails, you just run the test again so you get a green and the patch can be gated in.  So from that perspective if the tests pass on rerun the result is most useful if it is green.

Unless we want to say amber is OK for gating...but in terms of cognative load I think green is better.  After all, our current green state is morally equivalent to running the tests again and having them pass..
History
Date User Action Args
2015-07-29 21:37:48r.david.murraysetrecipients: + r.david.murray, zach.ware
2015-07-29 21:37:48r.david.murraysetmessageid: <1438205868.81.0.648770198589.issue24751@psf.upfronthosting.co.za>
2015-07-29 21:37:48r.david.murraylinkissue24751 messages
2015-07-29 21:37:48r.david.murraycreate