Open schumannd opened 4 years ago
It's not because you are on the free tier.
The most common cause of timeouts is something waiting for input. It's also not unheard of for a race condition to sometimes work and sometimes not. Have you tried rerunning a commit that worked before switching runtime versions to see if it still works? Did anything else change around the time you switched runtime versions that should be ruled out as the potential cause?
Most of the difference between different runtime versions is the versions of things installed. Although it's possible that one of the dependency versions may have a bug leading to the errors, nondeterministic errors are more often the result of updated code or the difference in memory and CPU available on the build node compared to locally, so it would be best to try to rule that out.
Thanks for the quick reply. I understand what you are saying. From our point of view these timeout errors started cropping up after updating to Runtime version 7.2.4 and subsided (so far) after downgrading to v 6.12.4
I will keep an eye on it, but hope that fixes it for now.
Latest timeout: https://app.shippable.com/bitbucket/davidmindance/mindancebackend/runs/2078/summary/console
Build soon to timeout (currently running for 45min): https://app.shippable.com/bitbucket/davidmindance/mindancebackend/runs/2078/summary/console
I can start experimenting with different Runtime Versions, but it seems to be nondeterministic. At least a build succeded here after changing nothing and simply rerunning from this timeout
Any Idea what could cause this? We are on free tier, could that be an issue?