On Mon, Aug 31, 2020 at 11:22 PM xiangdong...@gmail.com < xiangdong...@gmail.com> wrote:
> The issue happens at building time of 'go test' for misc/cgo/test, I was > expecting 'go test' is powerful enough to skip building a specific case > given a negation pattern and without involving tags, but just realized it's > a wrong way, 'go test' always builds all dependency stuff. > > Now the requirements are: > 1. not building Test7978 on arm64 when running the 'dist' test, and > 2. minimize the change so that it could be reverted easily when the link > issue gets fixed later. > > To disable the testing to misc/cgo/test for several 'internal linking' > cases on arm64 is an option, but that means other 90 tests are skipped > meanwhile. > Can you not leverage the and/or logic of `// +build` comments in the single unit test module affected by this issue to indicate that its tests should not be built or run unless a) the test is not being run on the "arm64" GOARCH, or b) the test is being run on the "arm64" GOARCH and the `Test7978` tag was specified. That would result in the test being run most of the time. When the bug you linked to is resolved you simply remove the custom build tag. You seem to have an aversion to using build tags for this problem, which I do not understand, while suggesting that introducing an equivalent mechanism is preferable. i don't understand why. -- Kurtis Rader Caretaker of the exceptional canines Junior and Hank -- 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/CABx2%3DD_jC%3Ddpi%3DTLVY4ugnJQVyk%3DEa3UG%3D9AXx1Av6M4oDqZgg%40mail.gmail.com.
