standard library tests in all.bash
If the compiler is broken, the standard library tests give us less
useful information than the compiler tests; the stdlib tests are
very likely to fail, and we won't get to the compiler tests to see
more useful failures.
In other words, the compiler tests and the compiler tests are more
fundamental than the standard library tests, so it makes sense (to
me) to run them before the standard library tests.
Most people work on the standard library, so if they break something,
it will take longer for all.bash to get to the failure.
To that I respond that people can use go test std before running
all.bash. This proposal is mostly about the builders. Sometimes the
compiler is broken, but we don't see exactly how because the compiler
tests don't run because the standard library tests failed.
Alternatives to this proposal:
Run compiler tests even if the standard library tests fail. Don't
stop, just keep going (in fact we used to do that for Plan 9 for a
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/d/optout.