On May 20, 2013, at 22:58 , Dirkjan Ochtman <[email protected]> wrote:
> On Mon, May 20, 2013 at 4:59 PM, Benoit Chesneau <[email protected]> wrote: >> I was thinking to the INSTALL doc. If e know that these versions are >> broken maybe we should tell it when the 1.3.1 will be released. >> >> Or just fix it, then I wonder why removing it. Maybe we need such >> pressure to fix these errors ;) > > I don't think those versions are strictly broken, since the failures > are intermittent, but it's sure nice if Travis doesn't fail so much. > And I'm not sure the pressure is high enough to get people to look at > intermittent issues? Also, Travis doesn't really seem to give a whole > lot of context to make it easy to see why tests fail (but that might > just be me). Nope, +1, that’s my reasoning as well. Ideally, once we have proper CI set up, we will be testing against all possible dependency combinations that we want to support, but can’t have that on Travis anyway, so we may as well slim this down a little and keep it around as a public sanity check. Jan --
