On Thu, Sep 1, 2016 at 11:24 AM, 'Tim Hockin' via golang-nuts <golang-nuts@googlegroups.com> wrote: > I was running tests against a new project, and it was really slow. > When I ran with -x I saw a bunch of build steps that didn't seem to be > necessary. Spelunking through docs, reveals that `go test` doesn't > install artifacts. `go test -i` does install artifacts but doesn't > run the tests. > > So I changed my script to always `go test -i` followed by `go test` > and lo, my tests run in 20% of the time. > > Am I doing something wrong? This feels really hacky - is it correct?
That is indeed how it works today. Usually I'm just working on one package, so I run `go test -i` once for that package and then don't worry about it until I'm working on a different package. I'm not sure how best to change this. It would seem weird for `go test` to install packages. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
