go: runtime: TestPhysicalMemoryUtilization test failures on various builders

A trybot run: https://storage.googleapis.com/go-build-log/25f64550/windows-386-2008_982c8967.log

step 1
step 8
step 9
step 10
step 11
step 12
step 13
step 14
--- FAIL: TestPhysicalMemoryUtilization (0.03s)
    malloc_test.go:246: expected "OK\n", but got "exceeded physical memory overuse threshold of 30.40%: 32.03%\n(alloc: 8581176, goal: 17384516, sys: 20840448, rel: 9510912, objs: 3)\n"
FAIL
FAIL	runtime	48.356s
FAIL

But I also see a few of this on https://build.golang.org (windows/386 builder).

cc @mknyszek

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 19 (17 by maintainers)

Most upvoted comments

Sigh. On it. At least it’s the same builders as the FreeOSMemory failure. Probably something to do with these platforms having 64 KiB pages.

mknyszek on Nov 11, 2021

I think we should strongly consider just marking it flaky for the moment while I try to figure something out here, again.

mknyszek on Nov 10, 2021

This bug is also reproducing on FreeBSD 32-bit builders. It seems more strongly correlated with a smaller address space, despite that darwin-amd64-nocgo failure.

https://build.golang.org/log/30765367d142efba9a1fdeaaedfdfdf3e57d1638 https://build.golang.org/log/d651f0b4d41d9bb05ea9667d100ce69fc6a6da34

mknyszek on Nov 9, 2021