x/tools: frequent "out of memory" errors on windows-amd64-race builder #39196
One difference between them is that the -race builder is using Windows server 2008, while -longtest is using Windows server 2016. Would it be a good first step to update the -race builder to a newer version of Windows? Or is it considered a benefit that it's testing with an older version of Windows?
…mage The purpose of the -race builder is to check for bugs on the Go side, so use the newer available Windows version with the expectation that there should be fewer unfixed bugs left in it. Take this easy step to eliminate a variable for issue golang/go#39196. Also delete host-windows-amd64-2008-big, since it's no longer used. For golang/go#39196. Change-Id: I9095a73ab21a151e5972219bccd5a16b249765b4 Reviewed-on: https://go-review.googlesource.com/c/build/+/235419 Reviewed-by: Carlos Amedee <firstname.lastname@example.org> Reviewed-by: Alexander Rakoczy <email@example.com>
My team sees a similar error very frequently when running lots of tests sequentially from Makefiles. Curiously adding a few seconds delay between tests appears to improve the stability (although, without hard statistics we might be fooling ourselves). Simply rerunning the tests is often enough for them to succeed.
This is using
This issue is a real nuisance for me and my team. We are very willing to help investigate and/or try potential fixes if anyone needs. Thanks!
Update at 2020-06-22: We have discovered that golang executables running out of memory is specific to executing our long "make" runs under powershell. Executing the same "make" runs under cmd.exe works correctly.
IWBN to understand the root cause though.
Only one OOM over the past year, but it's recent enough that I don't see any intervening changes that would have fixed it.