Skip to content
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

Jump to bottom

x/build/buildlet: allow configurable buildlet timeouts per buildlet #46398

Open
toothrot opened this issue May 26, 2021 · 0 comments
Open

x/build/buildlet: allow configurable buildlet timeouts per buildlet #46398

toothrot opened this issue May 26, 2021 · 0 comments
Labels
Builders x/build issues (builders, bots, dashboards) NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Go Release Team
Milestone
Unreleased

Comments

@toothrot
Copy link
Contributor

toothrot commented May 26, 2021 •
edited by dmitshur

Some buildlets take longer to start than others. Our default timeout was 5 minutes, which is reasonable for most cloud instances.

We recently added a a1.metal instance, which takes 5 minutes to boot, with additional time necessary to start a Windows ARM64 VM (#42604). We should be able to increase this timeout just for a one-off slow builder without making it wait unnecessarily long for everything.

See https://go.dev/cl/322654, which increased the timeout.
@toothrot toothrot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label May 26, 2021
@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label May 26, 2021
@gopherbot gopherbot added this to the Unreleased milestone May 26, 2021
@toothrot toothrot added this to Planned in Go Release Team Jun 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Builders x/build issues (builders, bots, dashboards) NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Go Release
Status: Planned
Go Release Team
Planned
Milestone
Unreleased
Development

No branches or pull requests
2 participants
@toothrot @gopherbot