Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
cmd/dist: infer GO_TEST_TIMEOUT_SCALE? #19508
The timeout scale is currently set based on a hard-coded list of architectures. Perhaps we should instead run a typical task (perhaps a
There's no terribly good way to do this purely in cmd/dist, because starting the tests is a different invocation than bootstrapping, so we can't just reuse (say) the time it took to
And what is the reason for the long work of the test? Do you examine these tests? Are there any computational tasks, math or parsing? Perhaps we should assume the maximum waiting time based on the slowest machine to current date? For example maximum time for 300 Mhz computer (like Pentium II)? I do not think that the testing time on such machines can be something limited, so you can specify quite large time intervals. Main reason is check compiler quality. In this case quality is prefer than time bounded.