Please make Travis CI optional again

[vstinner]

Please make Travis CI job optional on Python. The issue #376 prevents to merge PRs even when the Travis CI run succesfully.

---

For example, python/cpython#22513 was created 5 days ago. The PR lists two Travis CI builds. One is "Queued — Build Created", the other one is "Successful in 16m — Build Passed". Problem: if you click on the two builds... it's the same build: https://travis-ci.com/github/python/cpython/builds/188824091

Travis CI integration in GitHub is sick for several months and I'm tired of trying to fix it. Again, see #376 for the 3rd issue in 6 months.

[vstinner]

I'm not fully comfortable with having no mandatory Linux job on PRs. One solution would be to make the "Ubuntu (pull_request)" GitHub Action job mandatory.

What do you think of making the Travis CI job optional and make the Ubuntu job mandatory, at the same time?

Can this change be done for 3.7, 3.8, 3.9 and master branches? I see the Ubuntu job on my recent 3.7 PR: python/cpython#22578 (backport)

For Python 3.6, I see GitHub Action jobs, but only @ned-deily is allowed to merge changes on this branch. I'm sure that he will pay a special attention to all CIs before merging anything! Example of recent 3.6 PR: python/cpython#22579 (backport).

For 3.6, I suggest to just make Travis CI optional.

@ewdurbin @Mariatta @brettcannon: Who is allowed to make a CI mandatory or optional on the GitHub cpython project?

[ewdurbin]

@ewdurbin @Mariatta @brettcannon: Who is allowed to make a CI mandatory or optional on the GitHub cpython project?

Current organization owners and repository administrators

[ewdurbin]

When some consensus is determined, I'm happy to handle this, just mention me again.

[brettcannon]

I strongly support the proposed change.

[vstinner]

Once the change will be applied, I will notify python-committers list as I did last May when Travis CI became mandatory.
https://mail.python.org/archives/list/python-committers@python.org/message/B6WVI254L7GEOCKUOHZ6XBZD4GCLAIBV/

In May, Tracis CI looked reliable. Over time, it is getting worse and worse. I'm tired to spending time on trying to fix each Travis CI issue.

[ammaraskar]

I'm not fully comfortable with having no mandatory Linux job on PRs. One solution would be to make the "Ubuntu (pull_request)" GitHub Action job mandatory.

What do you think of making the Travis CI job optional and make the Ubuntu job mandatory, at the same time?

Given Travis's unreliability and their lack of any visible response or feedback on their forums I think this would be the best option for now. We should definitely have one mandatory Linux job and the Github workflow seems like a good replacement.

[Mariatta]

I also agree with making travisci not required for now.
I've brought up this issue with GitHub OS Maintainers feedback group. They said:

"The team responsible for Checks has been looking into this issue, but I'm not sure about a timeline for a fix"

[vstinner]

Given Travis's unreliability and their lack of any visible response or feedback on their forums

Oh right, I forgot to mention that "Travis CI fails to report build status to GitHub PR" is an old known issue and is frequently reported to the Travis CI community. I didn't see concrete progress over the last months.

[vstinner]

@ewdurbin: I count 3 people in favor of the making Travis CI optional, and no one who wants to keep it as mandatory. Would you mind to make it optional?

[ewdurbin]

@vstinner for all branches?

[ned-deily]

@vstinner for all branches?

Yes, please.

[ewdurbin]

Done.

[vstinner]

Done.

Thanks Ernerst! I announced the change on python-committers:
https://mail.python.org/archives/list/python-committers@python.org/thread/JR7HIQHVECHPKH2LE46EACN73KCBLVKE/

Now, should we consider to make the Ubuntu job mandatory, at least on the master branch, to get at least one Linux CI mandatory job?