-
Notifications
You must be signed in to change notification settings - Fork 17
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
Flaky CI runs #15
Comments
This is a good theory. Let's give it a shot. If you open a PR removing the timeout, will CI run without the timeout in that PR? |
There's an easy way to find out 😄 I'll get on that |
Resolved?? by #17 |
Originally posted by @kevin1024 in #11 (comment)
I've looked into the CI definition and saw just now that the jobs have a timeout of 10 minutes:
httpbin/.github/workflows/ci.yml
Line 11 in 7012f1a
This confirms my suspicion from my earlier post. I've noticed on a friend's laptop that docker is painfully slow on macOS. And - with an educated guess - I assume that the GitHub CI jobs run on docker containers.
This might explain the failures I had above. What do you think about either removing the timeout or increasing it considerably? Maybe we could remove it to get a rough feeling of how long those jobs take?
The text was updated successfully, but these errors were encountered: