You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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?
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?
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: