The timeout scale is currently set based on a hard-coded list of architectures. Perhaps we should instead run a typical task (perhaps a go build) and estimate the appropriate timeout scale from how long it takes.
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 go install std cmd; we'd have to do pointless work. We could do it in make.bash, although we'd have to replicate the logic to make.bat, make.rc, etc.
@bradfitz opinions?
Related: #19484
The timeout scale is currently set based on a hard-coded list of architectures. Perhaps we should instead run a typical task (perhaps a
go build) and estimate the appropriate timeout scale from how long it takes.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
go install std cmd; we'd have to do pointless work. We could do it in make.bash, although we'd have to replicate the logic to make.bat, make.rc, etc.@bradfitz opinions?
Related: #19484