plugin.so built with particular version of go cannot be loaded in any test package built with the same go version. From my perspective it basically limits possible usage of plugins as I cannot load and use plugins in tests and cannot test plugin itself in a test.

It cannot be loaded into a test that is inside a package included in the plugin. Try changing your test to a separate package, typically done by replacing the package declaration with package mypkg_test.

Already done that in the attached test case - result is the same (it seems that test package name doesn't matter at all). Also plugin cannot be loaded from any package used by the test itself.

In my case I've tracked this error while developing https://github.com/wendigo/go-bind-plugin which generates API for wrapping symbols exported by a plugin. I've got package cli that loads, analyzes symbols using reflection and generates code for the wrapper. When cli is used in a cli_test package plugin.Open fails to load it with an error: plugin was built with a different version of package runtime. It works just fine when loading it outside of the go test (also without cherry-picked https://go-review.googlesource.com/#/c/33161/ it works just fine).

Also I've noticed that for mismatched packages like runtime or os *pkghash.runtimehash is "" (empty string) when comparing it with non-empty pkghash.linktimehash in https://github.com/golang/go/blob/master/src/runtime/plugin.go#L45

Any news @crawshaw? I noticed that sometimes plugin cannot be also loaded outside the test (plugin.Open: plugin was built with a different version of package runtime) and when I've examined md.pkghashes only mismatched packages in my case were os and runtime (both with empty runtimehash). I don't know how runtimehash is exactly calculated.

Ping @crawshaw, @ianlancetaylor

CL https://golang.org/cl/33925 mentions this issue.

Fixed for me 👍 Thx @crawshaw