Thanks, that makes sense I guess. Would people be opposed to changing that behavior?
I’ve always thought of the time returned as the time to execute the command. Doesn’t matter to me if it’s having to compile or not. > On Apr 26, 2018, at 1:22 PM, Jan Mercl <[email protected]> wrote: > > time reports build+test time, but go test reports only test time. > >> On Thu, Apr 26, 2018, 18:54 Prateek Rungta <[email protected]> wrote: >> I've noticed weird discrepancies in the time reported by `go test >> <packages>`, and the elapsed wall clock time. >> >> For example: >> ❯ time go test ./client >> ok github.com/m3db/m3db/client 11.717s >> /Users/prungta/code/go1.9.2/bin/go test ./client 10.54s user 1.58s system >> 74% cpu 16.233 total >> >> ❯ time go test ./storage >> ok github.com/m3db/m3db/storage 4.830s >> /Users/prungta/code/go1.9.2/bin/go test ./storage 10.19s user 1.49s system >> 107% cpu 10.860 total >> >> How does `go test` calculate the time it reports? >> -- >> 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 [email protected]. >> For more options, visit https://groups.google.com/d/optout. > -- > -j -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
