CI: Travis CI has been completely disabled for SciPy (no credits left)
See original GitHub issuePlease be extremely cautious merging MRs into master as Travis CI has been completely disabled for SciPy and does not show up as a red or green mark in our testing matrix. This timing is a little unfortunate, just days before the planned branching of 1.6.0. We’re going to have to migrate the jobs to other services.
Here’s what I see in our Travis page:


Issue Analytics
- State:
- Created 3 years ago
- Comments:45 (39 by maintainers)
Top Results From Across the Web
Common Build Problems
Common Build Problems. My tests broke but were working yesterday; My build script is killed without any error; My build fails unexpectedly; Segmentation...
Read more >python - scipy ImportError on travis-ci
I removed -qq (see latest build here) and I see no problematic messages. If I open a terminal on my computer, yes, I...
Read more >Travis CI is no longer providing CI minutes for open source ...
How can they have written a letter only two weeks ago saying "Open source accounts, as always, will be completely free under travis-ci.com"?...
Read more >Travis CI's new pricing plan threw a wrench in my open ...
I have built projects for Raspberry Pi, PHP, Python, Drupal, Ansible, ... From the outset, Travis CI was built to integrate with GitHub ......
Read more >Migrating Your Open Source Builds Off Of Travis CI
TravisCI is no longer providing open source credits ... If you're not familiar with Travis CI, it's a build company that has been...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Hey @mattip I just pinged Travis folks to look at those you pasted above to make sure they were flowing through the queue. They have had a bit of backlog in the service queue but as you can see, they are trying to take this very seriously.
So far I’ve just migrated to Azure because I’m more familiar with. We may want to “load balance” a bit with GitHub actions in terms of straining the parallel limits.