Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
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?
The text was updated successfully, but these errors were encountered:
cmd/release: add flag to skip tests
Reviewed-by: Chris Broadfoot <firstname.lastname@example.org>
Sorry, something went wrong.
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.
This was a problem because I kept bumping into intermittent failures. Maybe those failures have stopped.
Let's re-open if releases get annoying again.
No branches or pull requests