-
Notifications
You must be signed in to change notification settings - Fork 79
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
add timeout on steps with network I/O #77
Conversation
well I guess that answers that question... you can't specify timeout-minutes in actions.yml https://github.com/tailscale/github-action/actions/runs/5414970481 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, but the CI failure is real.
Yeah, I don't think we can do this in actions.yml. timeout isn't mentioned in their docs, but I was hoping it would still work. Looks like users will need to set it on their own. Maybe we just update the README to suggest a default value. |
or maybe we use the |
I imagine curl has a timeout argument as well. |
Set a reasonable timeout to prevent jobs from hanging for hours (#50). 5 minutes is way longer than should ever be necessary, but accounts for intermittent networking issues on either the actions runner or the Tailscale package or control server. Users can always set a shorter timeout on their own action step. Fixes #50 Signed-off-by: Will Norris <will@tailscale.com>
Set a reasonable timeout to prevent jobs from hanging for hours (#50). 5 minutes is way longer than should ever be necessary, but accounts for intermittent networking issues on either the actions runner or the Tailscale package or control server. Users can always set a shorter timeout on their own action step.
Fixes #50