More Permanent Fix For Go 1.16 Module Usage Than Running With GO111MODULE Set To "off"
Go 1.16 has changed how projects are fetched and is even working towards changing how they are created and in what directories. They are moving towards a "Module Architecture" which is supposed to manage prereqs and coreqs inside Go-lang instead of relying on a 3rd party app.
This change has broken all of our testing on machines running Go 1.16. The directory is in a different place and the directory name has a version number encoded into it. This is easily demonstrated by changing the com/setupgoenv.csh and change the newly added setenv of GO111MODULE statement value from "off" to "on" (or running on a Go 1.16 machine). The change presents a number of difficulties including the fact that "go get" no longer pulls down the ".git" directory so the resulting directory is NOT a git directory that we can do things with.
Rather than not be able to run tests on some machines until we figure it out, we have made a change to com/setupgoenv.csh to set GO111MODULE to "off" which then reverts Go behavior to what it did for at least Go 1.7-1.15. The caveat with doing this is that GO111MODULE is to be ignored when Go 1.18 comes out in 6-12 months so this issue is to figure out a way around this. Just set GO111MODULE to "on" to start debugging the issue. @estess has some preliminary mods that might be a basis for this eventual change.