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: netbsd-arm64-bsiegert builder offline #65242

Closed
dmitshur opened this issue Jan 23, 2024 · 4 comments
Closed

x/build: netbsd-arm64-bsiegert builder offline #65242

dmitshur opened this issue Jan 23, 2024 · 4 comments
Assignees
@bsiegert
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

@dmitshur
Copy link
Contributor

https://ci.chromium.org/ui/p/golang/builders/ci/gotip-netbsd-arm64?limit=200 shows the last successful build was 14 days ago, and the builder is currently offline. It seems to need some attention, filing this issue to track that.

CC @bsiegert.
@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. labels Jan 23, 2024
@dmitshur dmitshur added this to the Unreleased milestone Jan 23, 2024
@bsiegert
Copy link
Contributor

The machine needed a hard reset. Fixed.

I have one more question: There are two arm64 builder machines. The one that was offline is running a gobuilder and a swarming bot. The other one is only running a gobuilder. I noticed there are tasks coming in on both of these. Is that intended?

@dmitshur
Copy link
Contributor Author

dmitshur commented Jan 29, 2024 •
edited

Thanks for resetting it.

The one that was offline is running a gobuilder and a swarming bot. The other one is only running a gobuilder.

Is that something you have control over on your side or is a change needed elsewhere? Since the second machine still connects to the old infrastructure, it seems better to update the machine that has both a swarming bot (new, LUCI) and buildlet (old, coordinator) to have just the former. That is, the optimal setup during this phase of the transition to LUCI would be:

  • 1 netbsd/arm64 machine receiving work from new LUCI (only)
  • 1 netbsd/arm64 machine receiving work from old coordinator (only)

When we get to switching to using LUCI as the primary system for post-submit and begin winding down the old system, you can update both machines to connect and receive work from LUCI.

@bsiegert
Copy link
Contributor

It's in my control.

This is good guidance, I will have one machine with the gobuilder and one with the swarming bot for now.

@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Jan 30, 2024
@gopherbot
Copy link

Change https://go.dev/cl/559504 mentions this issue: main.star: remove known issue for netbsd-arm64 builder

gopherbot pushed a commit to golang/build that referenced this issue Jan 30, 2024
@dmitshur @gopherbot
main.star: remove known issue for netbsd-arm64 builder
f3e6378 
The builder was restarted and came back.

For golang/go#65242.

Change-Id: I657fcb28793aac1def622ee1f85a129aaec39467
Reviewed-on: https://go-review.googlesource.com/c/build/+/559504
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
TryBot-Bypass: Dmitri Shuralyov <dmitshur@google.com>
Auto-Submit: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Michael Knyszek <mknyszek@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bsiegert bsiegert

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 @dmitshur @gopherbot