On Wed, 15 Feb 2017 at 15:23 Jean-Paul Calderone <exar...@twistedmatrix.com> wrote:
> > I wonder about the details of how treq's failures went unnoticed. Is > development sufficiently inactive that no one looked at CI between the > breakage and the release? Wasn't that a period of several months? Or does > it have a Twisted trunk@HEAD build that none of the contributors really > pay attention to? > The latter is the case; there are Twisted trunk builds, but they're flagged as "failures allowed" to avoid disrupting development with transient breakage. Unfortunately this means that basically nobody ever notices when they fail. For example, here's a failing build: https://travis-ci.org/twisted/treq/builds/194691849 I haven't found a good solution to this problem yet in my own projects; I'm hoping someone else has some ideas?
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
