Looks like it did fix the problem! Travis was also nice enough to reply to me on Twitter about our problem: https://twitter.com/travisci/status/869746712365150209.
On Tue, 30 May 2017 at 20:28 Mariatta Wijaya <mariatta.wij...@gmail.com> wrote: > I think this PR takes care of it. > https://github.com/python/cpython/pull/1879 > > > > On May 30, 2017 4:08 PM, "Brett Cannon" <br...@python.org> wrote: > >> At the moment Travis is not running the test build (it's actually not >> even listing it as a build). You can look at master, 3.6, or 3.5 to see >> that only the docs and coverage builds are being run: >> https://travis-ci.org/python/cpython/branches . I don't know why this is >> as it was fine yesterday and then stopped working today. The last change >> was from Antoine but its own Travis run ran fine so I don't think that >> caused the problem: >> https://github.com/python/cpython/commits/master/.travis.yml . If anyone >> can figure out if this is somehow our fault that would be great (I can't >> see how it is). >> >> But the key thing is to be aware that Travis being green just means the >> docs built fine. So until this is resolved, try to remember to check if the >> coverage test run passes if you want Travis to check your non-doc changes. >> >> _______________________________________________ >> python-committers mailing list >> python-committers@python.org >> https://mail.python.org/mailman/listinfo/python-committers >> Code of Conduct: https://www.python.org/psf/codeofconduct/ >> >>
_______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
