I thought of this a while back and decided not to do it. The tests ...
14 years, 2 months ago
(2011-02-11 23:03:34 UTC)
#2
I thought of this a while back and decided not to do it. The tests in
test/ are small tests, mostly compiler-related, and rarely break. I
almost never see a breakage there that isn't caught by the package
tests. On the other hand, package tests test the packages, which are
where most of the editing goes and most of the bugs happen. I say the
order is right as it stands.
For compiler writers I would favor a flag to invert the order, but the
current order should be the default.
-rob
On Fri, Feb 11, 2011 at 18:03, Rob 'Commander' Pike <r@golang.org> wrote: > I thought ...
14 years, 2 months ago
(2011-02-11 23:07:26 UTC)
#3
On Fri, Feb 11, 2011 at 18:03, Rob 'Commander' Pike <r@golang.org> wrote:
> I thought of this a while back and decided not to do it. The tests in
> test/ are small tests, mostly compiler-related, and rarely break. I
> almost never see a breakage there that isn't caught by the package
> tests. On the other hand, package tests test the packages, which are
> where most of the editing goes and most of the bugs happen. I say the
> order is right as it stands.
Okay. I'd still like to change the docs and the final print so
that it is clearer when everything is okay.
Issue 4183047: code review 4183047: build: run test/ directory first
(Closed)
Created 14 years, 2 months ago by rsc
Modified 14 years, 2 months ago
Reviewers:
Base URL:
Comments: 0