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: switch NetBSD and OpenBSD TryBots to builders that are not affected by known issues #50496

Closed
bcmills opened this issue Jan 7, 2022 · 1 comment
Closed

x/build: switch NetBSD and OpenBSD TryBots to builders that are not affected by known issues #50496

bcmills opened this issue Jan 7, 2022 · 1 comment
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. Soon This needs action soon. (recent regressions, service outages, unusual time-sensitive situations)
Milestone
Go1.18

Comments

@bcmills
Copy link
Contributor

bcmills commented Jan 7, 2022

In #49209, we identified particular NetBSD and OpenBSD configurations that produce frequent crashes in Go programs due to suspected upstream kernel bugs. We also identified particular platforms that do not appear to be affected by those bugs (namely, builders running on Intel processors), and the resulting -n2 variants of the builders have been running fairly reliably: they exhibit only a few test flakes that appear to be unrelated to the kernel bugs.

On CL 376334, I got a TryBot failure from an OpenBSD builder that appears to be due to #49209. Given that we have identified the affected platforms, that TryBot failure seems entirely avoidable: we could have simply run the TryBot on an unaffected instance instead.

We should reconfigure the NetBSD and OpenBSD TryBots to avoid the builder configurations with known problems.

(CC @golang/release)
@bcmills bcmills added Builders x/build issues (builders, bots, dashboards) NeedsFix The path to resolution is known, but the work has not been done. Soon This needs action soon. (recent regressions, service outages, unusual time-sensitive situations) labels Jan 7, 2022
@bcmills bcmills added this to the Go1.18 milestone Jan 7, 2022
@gopherbot gopherbot added this to the Unreleased milestone Jan 7, 2022
@bcmills bcmills modified the milestones: Unreleased, Go1.18 Jan 7, 2022
@heschi heschi self-assigned this Jan 7, 2022
@gopherbot
Copy link
Contributor

Change https://golang.org/cl/377474 mentions this issue: dashboard: clean up builders affected by memory corruption

@rsc rsc unassigned heschi Jun 22, 2022
@bsiegert bsiegert mentioned this issue Aug 30, 2022
Closed
@heschi heschi moved this to Done in Go Release Sep 27, 2022
@golang golang locked and limited conversation to collaborators Jun 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Builders x/build issues (builders, bots, dashboards) FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. Soon This needs action soon. (recent regressions, service outages, unusual time-sensitive situations)
Projects
Go Release
Archived in project
Milestone
Go1.18
Development

No branches or pull requests
3 participants
@bcmills @gopherbot @heschi