Go builds fail on filesystems that require UTF-8 filenames

[jvolkman]

I was trying out dbx_build_tools for our python project, but ran into an issue again that has been plaguing me for a while. The root cause is an upstream Bazel issue that I described in bazelbuild/bazel#12986.

Basically Go's source tree has one file - a test case for its own support for UTF-8 filenames - that causes Bazel to blow up on filesystems that require filenames to be UTF-8 encoded. Such filesystems include whatever macOS uses these days, as well as ZFS with the utf8only flag set (which happens to be the default on Ubuntu when enabling ZFS support at installation time). I've attached a screenshot of the build failure resulting when I run bazel build @dbx_build_tools//build_tools:bzl-gen.

rules_go added a workaround in bazel-contrib/rules_go#2836. It shells out to the system tar command for tar.gz go archives.

[benjaminp]

That's pretty unfortunate. I hate to add more system dependencies. I wonder if there's any possible scheme to just exclude the tests.