Home Original page

[python-committers] Bring back Travis & AppVeyor, make VSTS non-blocking

Terry Reedy tjreedy at udel.edu
Fri May 18 12:41:21 EDT 2018 
On 5/18/2018 12:25 AM, Gregory P. Smith wrote:
> VSTS is clearly not yet a stable continuous integration platform.  It 
> needs to be made non-blocking, and AppVeyor and Travis need to be 
> brought back!
> 
> Examples:
> https://github.com/python/cpython/pull/6938#issuecomment-389908094
>     Windows broke - 
> https://python.visualstudio.com/cpython/_build?buildId=522
> https://github.com/python/cpython/pull/6939
>     Linux broke - https://python.visualstudio.com/cpython/_build?buildId=523

Travis and AppVeyor are there on both issues, and both can be merged -- 
manually -- by pressing 'Squach and merge', even though not green.  The 
VSTS results are not blocking -- they are not marked as 'Required'.  The 
problem is that miss-islington was not changed, and sees any VSTS 
failure as a status check failure and a reason to not do the automerge 
you requested by approving the change.

> This was on a documentation-only change.
> 
> We cannot be changing to new PR-merge-blocking continuous integration 
> services at this point during a release cycle.  This is preventing 
> changes from making it in.

What *is* blocking merges and making them painful at times are the 
haphazard failures of test_asyncio on the blocking bots, Travis and 
AppVeyor, at a rate as high as 1/4 of individual test runs.  See
https://bugs.python.org/issue33531
On one backport last night, I had to run Travis 4 times, which means I 
had to periodically monitor the backport instead of approve and forget. 
And then I had to manually merge.

tjr
More information about the python-committers mailing list