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
When trying to build Go 1.0.3, TestCPUProfile fails on a VirtualBox with Fedora 16 as
its guest OS. I read somewhere that the IO APIC VBox setting is relevant here, and its
enabled. The build succeeds in Go 1.0.2.
Test output:
--- FAIL: TestCPUProfile (0.46 seconds)
pprof_test.go:57: profile too short: [0x0 0x3 0x0 0x2710 0x0 0x0 0x1 0x0]
FAIL
FAIL runtime/pprof 0.470s
uname -a:
Linux jsawdev 3.6.6-1.fc16.x86_64 #1 SMP Mon Nov 5 16:56:43 UTC 2012 x86_64 x86_64
x86_64 GNU/Linux
Relevant diff in pprof_test.go:
+ l := len(bytes) / int(unsafe.Sizeof(uintptr(0)))
val := *(*[]uintptr)(unsafe.Pointer(&bytes))
- val = val[:len(bytes)/int(unsafe.Sizeof(uintptr(0)))]
+ val = val[:l]
- if len(val) < 10 {
+ if l < 13 {
t.Fatalf("profile too short: %#x", val)
}
Let me know if I can provide any additional information. Thanks!
The text was updated successfully, but these errors were encountered:
profile too short means that the cpu is not delivering profiling events.
That's easy to believe in a virtualized environment, and of course profiling
is suspect in those environments anyway.
I wouldn't worry much about it.
I am a little surprised this changed from 1.0.2 to 1.0.3. I looked through the diffs,
and the only addition is the new EOD marker, and I don't see how that would affect this
unless it is mistakenly causing us to throw away profiles. But I can't see that it's
doing that.
Can you please confirm that it still works at 1.0.2 in your VM? If so, can you please
try running the test for both of these versions:
hg update -r 29990fa0951c
hg update -r 92e962e13197
If it works in the first but fails in the second then we have a problem.
Thanks.
I ran these builds a few times each and they don't consistently pass (and neither does
1.0.2 anymore). I've never run into this issue on any non-virtualized machines, so I'd
say the fault is with my VM as well. Thanks for looking into it though, sorry for the
inconvenience.
by jsawczuk:
The text was updated successfully, but these errors were encountered: