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.

Sign up for GitHub

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/internal/gomote: ensure that gomote activity renews the timeout for the instance #54398

Closed
cagedmantis opened this issue Aug 11, 2022 · 1 comment
Closed

x/build/internal/gomote: ensure that gomote activity renews the timeout for the instance #54398

cagedmantis opened this issue Aug 11, 2022 · 1 comment
Assignees
@cagedmantis
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
Go Release Team
Milestone
Backlog

Comments

@cagedmantis
Copy link
Contributor

When a gomote instance is actively being worked with then the instance should have the timeout period extended. This does not seem to be reliably happening.

@golang/release
@cagedmantis cagedmantis added Builders x/build issues (builders, bots, dashboards) NeedsFix The path to resolution is known, but the work has not been done. labels Aug 11, 2022
@cagedmantis cagedmantis added this to the Backlog milestone Aug 11, 2022
@cagedmantis cagedmantis self-assigned this Aug 11, 2022
@gopherbot
Copy link

Change https://go.dev/cl/422898 mentions this issue: internal/gomote, internal/coordinator/remote: keep gomotes alive

@joedian joedian added this to Done in Go Release Team Aug 16, 2022
@golang golang locked and limited conversation to collaborators Aug 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@cagedmantis cagedmantis

Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
Go Release
Archived in project
Go Release Team
Done
Milestone
Backlog
Development

No branches or pull requests
2 participants
@cagedmantis @gopherbot