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: gotip-netbsd-arm64 builder stops working #66963

Closed
cherrymui opened this issue Apr 22, 2024 · 3 comments
Closed

x/build: gotip-netbsd-arm64 builder stops working #66963

cherrymui opened this issue Apr 22, 2024 · 3 comments
Labels
Builders x/build issues (builders, bots, dashboards) NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Unreleased

Comments

@cherrymui
Copy link
Member

https://ci.chromium.org/ui/p/golang/builders/luci.golang.ci/gotip-netbsd-arm64

Looks like the builder is idle, but all builds before failed with infra failure.

cc @golang/netbsd
@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label Apr 22, 2024
@gopherbot gopherbot added this to the Unreleased milestone Apr 22, 2024
@cherrymui cherrymui added the NeedsFix The path to resolution is known, but the work has not been done. label Apr 22, 2024
@bsiegert
Copy link
Contributor

I run this bot.

It failed a build with BOT_DIED on April 19, and I rebooted it on April 21. It is now doing other tasks but it looks like tasks that came up while the bot was down are not automatically retried.

I asked on internal chat if I can have a notification for BOT_DIED tasks. Unfortunately, the storage in this Raspberry Pi (a USB HDD) is a bit flaky and occasionally goes into "Input/output error" mode.

@bsiegert
Copy link
Contributor

By the way, the bot wasn't idle, it ran tests on /x/ repositories.

@cherrymui
Copy link
Member Author

By the way, the bot wasn't idle, it ran tests on /x/ repositories.

https://ci.chromium.org/ui/p/golang/builders/luci.golang.ci/gotip-netbsd-arm64 this page showed it was idle when I looked this morning. Perhaps there was no commit to build at the time. I mostly meant to say it was not "Quarantined" or "Offline".

Thanks for resetting the builder. It seems to work well now. Let's call it fixed.

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) NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
3 participants
@bsiegert @gopherbot @cherrymui