Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

runtime/trace: TestTraceSymbolize failure on Windows #13116

Closed
ianlancetaylor opened this issue Oct 31, 2015 · 3 comments
Closed

runtime/trace: TestTraceSymbolize failure on Windows #13116

ianlancetaylor opened this issue Oct 31, 2015 · 3 comments
Labels
FrozenDueToAge OS-Windows
Milestone
Go1.6

Comments

@ianlancetaylor
Copy link
Contributor

According to build.golang.org, windows-386 is consistently failing with

addr2line: reading C:\Users\WINGOP~1\AppData\Local\Temp\go-build886867138\runtime\trace_test\trace.test.exe: runtime.pclntab and runtime.epclntab symbols must be in the same section
--- FAIL: TestTraceSymbolize (0.21s)
trace_stack_test.go:134: failed to symbolize trace: failed to read from addr2line: EOF
FAIL
FAIL runtime/trace 1.958s

This first report was http://build.golang.org/log/ced968d0310b82a3ea7bdd092d249123efccc159 while testing https://golang.org/cl/16070.
@ianlancetaylor ianlancetaylor added this to the Go1.6 milestone Oct 31, 2015
@alexbrainman
Copy link
Member

I cannot reproduce it here. But I will keep trying.

Alex

@aclements
Copy link
Member

I can't imagine how that CL would have directly caused this. It seems more likely this is a compiler/linker bug that this CL happened to tickle. It looks like it resolved itself with the latest commit to master.

I tried to reproduce this on the gomotes, but wasn't able to. @adg, @bradfitz, are there differences between the windows-386-gce builder on the dashboard and the VM created by gomote create windows-386-gce that would cause a test that fails reliably on the dashboard to not fail in the gomote VM?

@rsc
Copy link
Contributor

rsc commented Dec 5, 2015

Closing since we can't seem to reproduce it. If it comes back, we can debug it then.

@rsc rsc closed this as completed Dec 5, 2015
@golang golang locked and limited conversation to collaborators Dec 14, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge OS-Windows
Projects
None yet
Milestone
Go1.6
Development

No branches or pull requests
5 participants
@rsc @aclements @ianlancetaylor @gopherbot @alexbrainman