/ go Public
runtime: large initial values for GOMAXPROCS can cause runtime test failures #47246
Issues related to the Go compiler and/or runtime.
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
What version of Go are you using (
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
What did you do?
Run on systems with > 400 processors without a GOMAXPROCS setting.
On systems with fewer, set GOMAXPROCS=400.
What did you expect to see?
Correct test results.
What did you see instead?
When running on a system with > 400 processors, we are seeing some failures in the runtime package tests during ./all.bash that don't happen an explicit setting of GOMAXPROCS with a setting like 300. Some of these failures can be reproduced on systems with fewer processors if the initial GOMAXPROCS value is set to a number of about 400.
On a power9:
It seems that for ppc64le there should be a maximum default initial GOMAXPROCS value so that the runtime tests don't fail with the default setting.
We have seen other failures intermittently in the runtime package based on the GOMAXPROCS setting. Still trying to narrow down the conditions that cause those to fail.
The text was updated successfully, but these errors were encountered: