internal/trace/v2: OOMs in TestGCStress on 386 platforms #66624
Description
#!watchflakes
post <- pkg == "internal/trace/v2" && `out of memory` && goarch == "386"
Example failure: https://logs.chromium.org/logs/golang/buildbucket/cr-buildbucket/8752088278110881105/+/u/step/11/log/2.
I suspect this is just bad luck, and the uptick in failures might be correlated with an uptick in noise on our builders. The heap for this test isn't that big, but it does allocate extremely rapidly. It's within the realm of possibility that the GC is transiently failing to keep up, leading to enough memory use that we see failures on 386. I think we can avoid this by setting a memory limit because the actual live heap should be relatively small (last I checked, 50-60 MiB max).