Should we consider dropping Travis CI as a CI provider if it continues to be so flaky? Otherwise isn't it becoming just noise on a PR?

On Fri, Oct 16, 2020 at 1:42 AM Victor Stinner <> wrote:

Python has no mandatory Linux CI job on pull requests anymore. Right
now Windows (x64) remains the only mandatory job. Please be careful to
manually check other CI before merging a PR.


We had to deal with at least 3 different issues on the Travis CI over
the last 6 months. The latest one (3rd issue) is on the Travis CI side
and is known for months. Sometimes, a Travis CI build completes but
the GitHub pull request is never updated. Since Travis CI was
mandatory, it was never possible to merge some pull requests. I also
noticed a 4th bug, sometimes a PR gets *two* Travis CI jobs on a PR
for the same Travis CI build, only one is updated, and so again, the
PR cannot be merged.

For all these reasons, Travis CI was made optional.

I would be nice to have a mandatory Linux job: "Tests / Ubuntu
(pull_request)" is a good candidate. But I didn't check if it's
reliable or not.

See for the discussion.

Note: if someone manages to fix all Travis CI issues, we can
reconsider making it mandatory again. But it seems like most people
who tried (included me) are tired or bored by Travis CI.

Night gathers, and now my watch begins. It shall not end until my death.
python-committers mailing list --
To unsubscribe send an email to
Message archived at
Code of Conduct: