-
-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Travis CI #422
Comments
They are, but the feedback loop github<>travis has issues E.g. for #420 there is https://travis-ci.org/github/thephpleague/commonmark/builds/670958523 I've seen the same issue on my public repos. Will probably just move to github actions 😄 |
If you do their migration to travis-ci.com, then things should work? |
(from .org) |
Thank you both! Migrating seemed to fix things :) |
@GrahamCampbell nice info, is there any background why this is required? |
.com uses newer (2017...) apis, basically. .org should still work but it looks travis messed it up, so. |
Just kidding, it's broken again, and I've tried everything I could think of to fix this. I've submitted a support ticket to Travis CI Support - hopefully they can point me in the right direction. |
It really happens in a lot of projects, e.g. botman/botman#1134 (comment) |
Definitely seems to be travis' fault. Other CI services are having no trouble writing statuses. |
Ah, looks like they were doing maintenance: https://www.traviscistatus.com/incidents/xw5h6qv25mk1 Builds are magically working again! 🎉 |
CI tests aren't running 🙀
The text was updated successfully, but these errors were encountered: