x/build: fix, stabilize netbsd/386 port

[4a6f656c]

There has not seemingly been a netbsd/386 builder for a number of years - given that a builder is a requirement for a port, is it time to remove netbsd/386?

https://github.com/golang/go/wiki/PortingPolicy

[bradfitz]

We have plenty of x86 compute resources to run a netbsd-386 builder and we used to run one.

The builder's not the issue.

The issue was that the builder was super flaky, IIRC. (There are probably old bugs about turning it off and its flakes)

I'd rather see some attention paid to fixing it up.

[krytarowski]

netbsd/386 builder for a number of years like.. 1 year?

[krytarowski]

golang for i386 has some users and it works good enough, but some corner cases are flaky.

[bradfitz]

I just tried to run the builder. It hangs somewhere in the runtime tests ("go test -short runtime").

@krytarowski, I'm happy to re-enable the builder if you can even get it to 50% reliably passing, as long as it doesn't hang.

[bradfitz]

Previously: #25206 in which @bsiegert said it was passing. Maybe not on GCE?

[gopherbot]

Change https://golang.org/cl/174637 mentions this issue: dashboard: add darwin-amd64-nocgo config, remove nacl-386 trybot

[krytarowski]

I'm still busy with !golang so cannot make any promises myself.

[bsiegert]

And it still passes, I tried in VirtualBox yesterday.

Given how close we are to branching NetBSD 9, maybe running the 386 builder on -current would make sense?

[bradfitz]

And it still passes, I tried in VirtualBox yesterday.

Did you test 8 or current?

8 on GCE doesn't work. I tried 3 days ago (see above).

[krytarowski]

Using HEAD / -9 is a good idea. There were many improvements.