go: runtime: TestLldbPython failing with 'no intvar'
During all.bash, I 100% reproducibly get:
--- FAIL: TestLldbPython (7.82s)
runtime-lldb_test.go:187: Unexpected lldb output:
Created target
Created breakpoint
Process launched
Hit breakpoint
Stopped at main.go:10
no intvar
FAIL
FAIL runtime 35.143s
On macOS.
$ lldb --version
lldb-1001.0.12.1
Swift-5.0
The builders aren’t failing because of https://github.com/golang/go/issues/31123.
About this issue
- Original URL
- State: open
- Created 5 years ago
- Comments: 23 (18 by maintainers)
Commits related to this issue
- runtime: skip broken TestLldbPython It's broken on our builders (once we enabled dev mode on our Macs, see CL 170339) Updates #31188 Change-Id: Iceea65dc79576057b401a461bfe39254fed1f7ed Reviewed-on... — committed to golang/go by bradfitz 5 years ago
- [release-branch.go1.12] runtime: skip broken TestLldbPython It's broken on our builders (once we enabled dev mode on our Macs, see CL 170339) Updates #31188 Change-Id: Iceea65dc79576057b401a461bfe3... — committed to golang/go by bradfitz 5 years ago
- cmd/link: revert/revise CL 98075 because LLDB is very picky now This was originally Revert "cmd/link: fix up debug_range for dsymutil (revert CL 72371)" which has the effect of no longer using Base... — committed to golang/go by dr2chase 5 years ago
It’s not good that it causes all.bash to fail for Mojave users. “Fix soon” assumes that “soon” is an actual option for “fix”.
Gdb worked for me last week, but not this week. Seriously. I even code-signed it just now, but for some reason that didn’t work. Presumably security was enhanced in some way when I upgraded to Mojave.