Open
Description
At b84e0bc, on darwin/amd64:
$ go test -run=TestDWARF/testprog -count=10 cmd/link
--- FAIL: TestDWARFiOS (0.53s)
--- FAIL: TestDWARFiOS/testprog#03 (2.03s)
dwarf_test.go:96: exit status 255
--- FAIL: TestDWARFiOS (0.50s)
--- FAIL: TestDWARFiOS/testprog#03 (1.78s)
dwarf_test.go:96: exit status 255
--- FAIL: TestDWARFiOS (0.52s)
--- FAIL: TestDWARFiOS/testprog#03 (1.96s)
dwarf_test.go:96: exit status 255
--- FAIL: TestDWARFiOS (0.54s)
--- FAIL: TestDWARFiOS/testprog#03 (1.83s)
dwarf_test.go:96: exit status 255
--- FAIL: TestDWARFiOS (0.53s)
--- FAIL: TestDWARFiOS/testprog#03 (1.98s)
dwarf_test.go:96: exit status 255
--- FAIL: TestDWARFiOS (0.54s)
--- FAIL: TestDWARFiOS/testprog#02 (1.99s)
dwarf_test.go:96: exit status 255
FAIL
FAIL cmd/link 47.577s
FAIL
I've also seen
--- FAIL: TestDWARF (0.22s)
--- FAIL: TestDWARF/testprog (3.00s)
dwarf_test.go:96: exit status 255
FAIL
The failures are intermittent.
cc @dr2chase
Metadata
Metadata
Assignees
Labels
Type
Projects
Relationships
Development
No branches or pull requests
Activity
cherrymui commentedon May 24, 2019
Happened for me as well, with exactly same error. I commented on CL https://go-review.googlesource.com/c/go/+/170377
odeke-em commentedon Jun 23, 2019
Running on c11f6c4
uname
uname -a Darwin Emmanuels-MacBook-Pro-2.local 18.5.0 Darwin Kernel Version 18.5.0: Mon Mar 11 20:40:32 PDT 2019; root:xnu-4903.251.3~3/RELEASE_X86_64 x86_64
On the first try I get a failure but this time spectacularly with a 1.2MB log whose beginning is something like
with the output at https://gist.github.com/odeke-em/85bb51ded80d9239a97c435f875b04c5
aclements commentedon Jun 27, 2019
Some notes:
As far as I can tell, this has never happened on the dashboard based on
greplogs -E 'dwarf_test.*(exit status 255|symbols)' -dashboard
.CL 171819 added better logging for this (previously we didn't print the symbols output). That's why the original report just has "exit status 255", but @odeke-em's report has much more information.
Unfortunately, it seems like the symbols tool may just be flaky. Just searching around for that error reveals other people seeing it occasionally in various macOS development tools outside the context of Go.
Could someone with a Mac try just running symbols (or maybe the test) in a loop to see how often it flakes?
dr2chase commentedon Jun 27, 2019
It may require Darwin 18.5, which is one back from current.
I've tried running it in a loop with luck at seeing the bug, will try some more.
(Maybe a busy Mac helps?)
dr2chase commentedon Jun 27, 2019
About 2000 repetitions on Darwin 18.6 (aka Mojave, macOS 10.14.5), with no failure, on a busy-ish machine. Still running.
ianlancetaylor commentedon Aug 2, 2019
In the output above the symbols program completes, but then reports an error
symbols[65885]: [fatal] child process status could not be determined; exit code unavailable.
I can see the error string if I run strings on /usr/bin/symbols, so it's definitely coming from there. I can't find any reports of this error on the Interwebs (the top search result for me is in fact this issue). I don't know why the symbols program would start a child process at all. I don't know why it would be unable to determine the status of that child process. I can't find the source code of the symbols program; I don't know if it is available at all.Moving to 1.14 but if we can't figure out a reproducer, or get the source code, I doubt there is much that we can do.
ianlancetaylor commentedon Nov 15, 2019
Is this still happening for anyone?
9 remaining items