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/cmd/coordinator: add health item for work queue size and errors in finding work #43326

Open
dmitshur opened this issue Dec 22, 2020 · 0 comments
Open

x/build/cmd/coordinator: add health item for work queue size and errors in finding work #43326

dmitshur opened this issue Dec 22, 2020 · 0 comments
Labels
Builders x/build issues (builders, bots, dashboards) FeatureRequest NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Backlog

Comments

@dmitshur
Copy link
Contributor

When issue #43312 was reported, https://farmer.golang.org/#health displayed all green health items. Looking into coordinator logs showed that the findTryBotLoop was having very frequent errors. We expect no errors to happen under normal operation.

It would be helpful to add health items to https://farmer.golang.org/#health that make it more visible when there are recent errors in finding work (both TryBot work, and post-submit work; they're different queues).

CC @golang/release.
@dmitshur dmitshur added 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. FeatureRequest labels Dec 22, 2020
@dmitshur dmitshur added this to the Backlog milestone Dec 22, 2020
@dmitshur dmitshur mentioned this issue Dec 22, 2020
Closed
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) FeatureRequest NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
1 participant
@dmitshur