Travis is in the middle of moving everything from AWS to GCE, which is probably related:
https://blog.travis-ci.com/2018-11-19-required-linux-infrastructure-migration As noted there, GCE has different IP addresses. But I suspect it's not the new IP address that's the problem, but rather the fact that the GCE setup is known to break outgoing ftp: https://blog.travis-ci.com/2018-07-23-the-tale-of-ftp-at-travis-ci -n On Wed, Dec 5, 2018, 02:53 Victor Stinner <vstin...@redhat.com wrote: > Hi, > > It seems like Travis CI changed its security or network configuration: > some FTP tests of test_urllib2net started to fail with "425 Security: > Bad IP connecting" yesterday: > > https://bugs.python.org/issue35411 > > The failure seems to be reproducible and so prevents to merge any > change in any branch. It blocked our whole workflow :-( > > Good news: I quickly fixed the CI! (2.7, 3.6, 3.7 and master branches) > I skipped the test on Travis CI: AppVeyor runs these tests in > pre-commit and the buildbot farm run them in post-commit. > > Bad news: You may have to update your pull requests (ex: merge master > into your branch) to retrieve this fix if the test_urllib2net failed > on Travis CI with "425 Security: Bad IP connecting" on your PR. > > Victor > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/njs%40pobox.com >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
