You could try using Delve (https://github.com/derekparker/delve) to
actually step through and inspect the process during execution to avoid
having to put print statements everywhere. Similar to the Go command, you
can run `dlv test` and begin stepping through your test binary.
On Thursday, Nove
Some ideas:
- I assume the code isn't public? If it is, you might share it
- Are you running `go test -v` for verbose logging?
- Try fmt.Printf
- Try adding printing lines at points down the stack leading up to the
point you think is failing, to make sure the code is actually running.
- Put a log
