[python-committers] AppVeyor and Travis-CI (original) (raw)

Brett Cannon brett at python.org
Tue May 15 11:23:00 EDT 2018

You can always close and then open an issue to re-trigger CI. As for Travis specifically, you should have the proper permissions to forcibly re-run the builds.

On Mon, 14 May 2018 at 21:50 Eric V. Smith <eric at trueblade.com> wrote:

I accidentally checked in some test files, and they got backported to 3.7. I pushed a commit to delete them, and it was committed to master.

But in the 3.7 backport, something has gone wrong with AppVeyor and Travis-CI. https://github.com/python/cpython/pull/6844 AppVeyor says "Expected — Waiting for status to be reported". There's no obvious way to get it to actually report the status, or to restart. There is no "Details" button listed on the PR page. For Travis-CI, Miss Isslington sent me an email that says "Backport status check is done, and it's a failure ❌ ." The Travis-CI log file ends with a timeout: ====================================================================== FAIL: teststdinbrokenpipe (test.testasyncio.testsubprocess.SubprocessSafeWatcherTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/travis/build/python/cpython/Lib/test/testasyncio/testsubprocess.py", line 214, in teststdinbrokenpipe self.loop.rununtilcomplete, coro) AssertionError: (<class 'BrokenPipeError'>, <class_ _'ConnectionResetError'>) not raised by rununtilcomplete ---------------------------------------------------------------------- I'm sure this is all due to the heavy load the systems are under. I can't find a way to kick both of these off again. I couldn't find anything in the devguide, but if I missed it please let me know. Thanks. Eric

python-committers mailing list python-committers at python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20180515/e6c5121c/attachment.html>

More information about the python-committers mailing list