-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
Setting CircleCI's no_output_timeout
parameter
#784
Comments
I guess the question is how often people's builds mistakenly deadlock, versus how often they need the longer timeout. My guess is that both are relatively rare; I can't remember seeing either more than a handful of times. |
Timeouts are fairly common in long running/complex builds. A fair bit of time is spent tinkering with this sort of thing by maintainers. Certainly users can set this themselves if they know to (good argument for documenting at least). The main issues are re-renderings removing this setting and users not being aware this is an allowed option. Admittedly this would be more valuable if we could set this more uniformly across CIs. |
Opened issue ( travis-ci/travis-ci#9666 ) with Travis CI about getting a similar option. On AppVeyor's issue tracker, issue ( appveyor/ci#517 ), which is similar, has already been raised. |
Done in PR ( #973 ). |
Setting CircleCI's
no_output_timeout
parameter generally to avoid timeouts w.r.t. long quiet builds. We could just generally set this or make it an opt-in parameter inconda-forge.yml
. Thoughts?The text was updated successfully, but these errors were encountered: