x/build: "fatal error: out of memory" on windows-arm64-11

[bcmills]

#!watchflakes
post <- builder ~ `^windows-arm64.*` && `fatal error: .*(?:out of memory|cannot allocate memory|The paging file is too small|Insufficient system resources)`

greplogs --dashboard -md -l -e '(?ms)\Awindows-arm64.*^fatal error: out of memory' --since=2021-01-01

2022-02-04T14:02:15-25d2ab2-4afcc9f/windows-arm64-11

We may need to reconfigure the builder to either turn down the build/test parallelism or have more RAM available.

There is only one of these failures in the logs, but OTOH this builder has only ever run x/tools 12 times — so that's an 8% failure rate for this repo so far. 😅

(attn @golang/release)

[heschi]

So far I'm not seeing any recurrences on what I assume is a much higher number of runs. We can keep an eye on it but right now I'm inclined to leave it alone.

[bcmills]

So far I'm not seeing any recurrences

Here's one running x/crypto:

greplogs --dashboard -md -l -e '(?ms)\Awindows-arm64.*^fatal error: out of memory' --since=2022-02-05

2022-02-10T15:16:21-f4118a5-656d3f4/windows-arm64-11

[bcmills]

From the sheer number of packages that failed in each of those logs, I suspect that the parallelism is being set to high. What's the CPU-to-RAM ratio for this builder? (Maybe we could scale down GOMAXPROCS?)