We have some tests that are pretty slow. I would like to use Go's test caching to skip them in our CI environment, if nothing in the code or the environment has changed. Our CI environment has a set of _agents_, each of which can run multiple jobs simultaneously. As a result, they check out code into a different directory each time they run a job.
Go's test caching checks every env var loaded by the test program. If any of them change, then Go assumes that the cache is busted and the test must be run. Any program that imports "os" hits this logic in the os package, which checks the value of the $PWD environment variable: // We query the working directory at init, to use it later to search for the // executable file // errWd will be checked later, if we need to use initWd var initWd, errWd = Getwd() So checking code out to different directories means that any program that imports "os" cannot have test caching. This seems like a shame because the code is all laid out in the same place in the working directory. Has anyone tried to fix this issue? Do you think this is worth trying to patch or modify the test caching behavior in Go itself? I could solve this by running a chroot or another layer of Docker, of course, but I'd prefer not to do these because of the difficulty of getting data in and out of each one, communicating with other Docker containers, etc. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/93132985-d1cc-4bdc-abfb-6fb519d62c54n%40googlegroups.com.
