You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TestLinkerGC in crypto/tls has started failing on pppc64le. The test is skipped in short mode so the failure does not show up on the build dashboard.
What version of Go are you using (go version)?
$ go version
latest
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
ppc64le
What did you do?
Tried to run the tests in crypto/tls (not using -short) and saw this failure.
What did you expect to see?
PASS
What did you see instead?
cd crypto/tls && go test -c
./tls.test
--- FAIL: TestLinkerGC (2.72s)
--- FAIL: TestLinkerGC/empty_import (0.73s)
link_test.go:102: unexpected symbol "tls.(*Conn)" found
FAIL
This started with commit 537cde0 cmd/compile, runtime: add metadata for argument printing in traceback @cherrymui
The text was updated successfully, but these errors were encountered:
TestLinkerGC in crypto/tls has started failing on pppc64le. The test is skipped in short mode so the failure does not show up on the build dashboard.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Tried to run the tests in crypto/tls (not using -short) and saw this failure.
What did you expect to see?
PASS
What did you see instead?
cd crypto/tls && go test -c
./tls.test
--- FAIL: TestLinkerGC (2.72s)
--- FAIL: TestLinkerGC/empty_import (0.73s)
link_test.go:102: unexpected symbol "tls.(*Conn)" found
FAIL
This started with commit 537cde0 cmd/compile, runtime: add metadata for argument printing in traceback
@cherrymui
The text was updated successfully, but these errors were encountered: