Consider dropping (the "required" state for) Travis?

[brettcannon]

Personal experience with CPython says all CI fails, so you either don't require any of them or you stick with one and deal with its shortcomings rather than dealing with N tools' shortcomings.

Travis is currently not returning any status and since it's required I can't merge any PRs without an admin override. I'm personally fine just going with GitHub Actions as I don't think Travis adds much benefit. But if people want to keep it then can we consider changing the status check requirement for it?

[di]

Something odd is going on with our Travis-CI account:

Builds have been temporarily disabled for private and public repositories due to a negative credit balance. Please go to the Plan page to replenish your credit balance.

(cc @ewdurbin)

[di]

If we're fully ported to GitHub Actions, I don't see any reason to continue using Travis here (especially if we're consuming credits that other PyPA projects may actually need more than us).

[pradyunsg]

I'd say let's just take out Travis CI.

[brettcannon]

I think the IRC integration is the only thing we are missing, otherwise we actually have integrated with GHA than Travis at this point.

I have gone ahead and turned off the webhook to see how this goes. If it works out then we can delete the hook, .travis.yml and ask someone to remove the Travis integration (I don't appear to have the appropriate permissions; maybe org admin can do it?).

[pradyunsg]

Given that I have travis-ci muted in IRC, I don't think anyone cares about that integration at this point. :)

Your plan sounds great to me!

[brettcannon]

I've tweaked the status check requirements to only be GHA so that we control it while we see how this goes. I say we give it a month, and if it works out then we can drop Travis.

[mayeut]

Does anybody here have a clue what's happening with our Travis-CI account or if there's someone in charge of that account ?
I guess we had some (maybe free) credits credited every day/month since travis-CI changed its policy and up-until end of January but that stopped for some reason ?
Happy to take this discussion elsewhere but I'm not sure discuss.python.org is appropriate.

[di]

It looks like on Jan 29th, Travis switched us to a free plan with 10K build credits, but we're currently in a hole of -930 credits that we're not recovering from. I reached out to support.

[di]

The PyPA travis account has been temporarily restored, but I'd still encourage this project (and others) to migrate to Actions.

[mayeut]

Thanks for the feedback @di
Could you expand a bit on "temporarily" ?

pypa/manylinux & pypa/auditwheel could really benefit from travis-ci for aarch64/ppc64le/s390x where those architectures are natively supported (using qemu on GHA works but gives a build time of nearly 5 hours vs 30-40 minutes on travis-ci).