Home Original page

[python-committers] AppVeyor and Travis-CI

Guido van Rossum guido at python.org
Tue May 15 14:02:56 EDT 2018 
IIUC you have to close and reopen the PR.

On Tue, May 15, 2018 at 11:35 AM, Eric V. Smith <eric at trueblade.com> wrote:

> Thanks. You mean close and re-open the bpo issue?
>
> In the past I saw a Travis "re-run" button, but now I don't. I expected to
> see it on the Travis page, but last night I only saw a "More options" menu
> and no "re-run". The next time something fails I'll look again.
>
> On 5/15/18 11:23 AM, Brett Cannon wrote:
>
>> 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
>> <mailto: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: test_stdin_broken_pipe
>>     (test.test_asyncio.test_subprocess.SubprocessSafeWatcherTests)
>>     ------------------------------------------------------------
>> ----------
>>     Traceback (most recent call last):
>>        File
>>     "/home/travis/build/python/cpython/Lib/test/test_asyncio/tes
>> t_subprocess.py",
>>
>>     line 214, in test_stdin_broken_pipe
>>          self.loop.run_until_complete, coro)
>>     AssertionError: (<class 'BrokenPipeError'>, <class
>>     'ConnectionResetError'>) not raised by run_until_complete
>>     ------------------------------------------------------------
>> ----------
>>
>>     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 <mailto:python-committers at 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 at python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>



-- 
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20180515/047a9174/attachment.html>
More information about the python-committers mailing list