I have been wondering why testing on my Windows 8.1 machine takes forever, turns out Avast’s DeepScreen tries to analyze every go binary and therefore slows the entire process down by a factor of more than 10 if not 100.
Since I could never find an answer on the internet why it took so long, I’m writing this down for future generations of Gophers.
Runtime comparison
with Avast DeepScreen:
PASS
ok github.com/example/ftree 27.816s
without:
PASS
ok github.com/example/ftree 0.216s