Builds stuck in Received state

We’re in the process of preparing a release and since yesterday afternoon, our builds in one repo have been stuck in the “Received” state, not even advancing to queued.

We saw there is a notice on that notes “Experiencing Issues with GitHub API Requests” and “under maintenance.” If this the likely cause of our issue, and is there an ETA for resolution?

Our release timeline may be impacted by this, so we’d like to get as much info as possible to troubleshoot. Thank you!

This is affecting many people as Travis is moving infra from .org to .com.

You may be best migrating over to .com, especially if it’s delaying your release, but note build history may or may not be migrated too:

1 Like

What is the expected timeline for this? Is this temporary (couple of more hours) ? The FAQs suggest the migration is planned to finish by Dec 2020 so are we to expect such degraded behavior till then?

I’ve no idea, but they talk of moving infra from .org to .com, so I get the impression it’s not going to improve much on .org, unless a lot of people migrate to .com and free more resources on .org? But then will more infra be moved to .org?

At present it is not clear that moving to the .com will improve the build waits - the statistics shown (on the number of Linux jobs being run) on {note the “.com” in the URL!} make for depressing reading over the last week.

Obviously not moving won’t be good in the long term (beyond the end of 2020) as then the .org site will then only be usable to see how historic builds went.

I am also experiencing the same issue.
It’s been stuck for 11 hours now…

Can you please check on the build Travis CI - Test and Deploy Your Code with Confidence

Thank you