Thanks for the awesome project!
I'm seeing an odd issue: running my test suites with ginkgo takes significantly longer than running them with go test:
$ time go test -tags unitTests ./server/...
ok github.com/batect/abacus/server/api 0.496s
ok github.com/batect/abacus/server/cmd 0.335s
ok github.com/batect/abacus/server/middleware 0.195s
? github.com/batect/abacus/server/middleware/testutils [no test files]
ok github.com/batect/abacus/server/storage 0.173s
2.69 real 5.60 user 1.93 sys
$ time ~/go/bin/ginkgo -tags unitTests server/...
[1581318849] API Suite - 46/46 specs •••••••••••••••••••••••••••••••••••••••••••••• SUCCESS! 2.535598ms PASS
[1581318849] Application Suite - 0/0 specs SUCCESS! 241.13µs PASS
[1581318849] Middleware Suite - 9/9 specs ••••••••• SUCCESS! 778.471µs PASS
[1581318849] Storage Suite - 3/3 specs ••• SUCCESS! 206.337µs PASS
Ginkgo ran 4 suites in 4.485361489s
Test Suite Passed
4.49 real 9.35 user 5.09 sys
I've tried setting -compilers to a low number as suggested in #258, but this doesn't have a significant impact.
batect/abacus@f8d4c57 is the commit I'm testing this on.
Thanks for the awesome project!
I'm seeing an odd issue: running my test suites with
ginkgotakes significantly longer than running them withgo test:I've tried setting
-compilersto a low number as suggested in #258, but this doesn't have a significant impact.batect/abacus@f8d4c57 is the commit I'm testing this on.