Russ Cox has an experimental command called gt, which replaces the go test
tool, and caches test output when you run it. The next time you run gt, if
none of the files in a package have changed and none of the files of
packages it depends on have changed, then gt will just reprint the cached
outpu
On 15/06/2015, Nate Finch wrote:
> Russ Cox has an experimental command called gt, which replaces the go test
> tool, and caches test output when you run it. The next time you run gt, if
> none of the files in a package have changed and none of the files of
> packages it depends on have changed,
Well, yes. Actually, this happened to me the first time I ran gt... I had
a couple different intermittent failures, which were then helpfully cached.
:/ You can always force a re-run with gt -f to get out of this situation,
but it's far better to just make our tests deterministic.
On Mon, Jun 15
