You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cmd/release used to be fast and only ran make.bash.
Now it runs all.bash, which is slow.
But if all.bash already succeeded in the past there's no need to run the tests again. Maybe consult build.golang.org and ask if it already succeeded, and then switch to make.bash instead?
I rolled the binaries yesterday and didn't think they took a particularly long time. The ARM ones, maybe. I feel like this is just optimizing for little real benefit.
Also—not that I distrust our build infrastructure, but—I feel there is some value in running the tests one last time before handing over binaries to our users.
cmd/release used to be fast and only ran make.bash.
Now it runs all.bash, which is slow.
But if all.bash already succeeded in the past there's no need to run the tests again. Maybe consult build.golang.org and ask if it already succeeded, and then switch to make.bash instead?
/cc @broady
The text was updated successfully, but these errors were encountered: