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.

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

runtime/pprof: TestCPUProfileMultithreaded is flaky on ppc64le #13223

Closed
mwhudson opened this issue Nov 13, 2015 · 7 comments
Closed

runtime/pprof: TestCPUProfileMultithreaded is flaky on ppc64le #13223

mwhudson opened this issue Nov 13, 2015 · 7 comments

Comments

@mwhudson
Copy link
Contributor

For example from http://build.golang.org/log/a58e91460d1b6bec7380bd3f9f86f57483aa2e22:

--- FAIL: TestCPUProfileMultithreaded (0.25s)
    pprof_test.go:165: total 12 CPU profile samples collected
    pprof_test.go:181: runtime/pprof_test.cpuHog1: 0
    pprof_test.go:181: runtime/pprof_test.cpuHog2: 12
    pprof_test.go:195: runtime/pprof_test.cpuHog1 has 0 samples out of 12, want at least 1, ideally 6
FAIL

Very old neurons recall that the timer on powerpc has pretty low resolution, but I don't know if that is true or the problem here.

@rsc rsc added this to the Go1.6Maybe milestone Dec 28, 2015
@aclements
Copy link
Member

@davecheney, can you provide the kernel config for the linux-ppc64le-canonical builder? In particular, if CONFIG_HIGH_RES_TIMERS is not set, this is probably the same as #13405.

@aclements
Copy link
Member

I'm guessing it's this one: http://kernel.ubuntu.com/~kernel-ppa/configs/trusty/ppc64el-config.flavour.generic, which does have CONFIG_HIGH_RES_TIMERS set.

@rsc
Copy link
Contributor

rsc commented Jan 6, 2016

@aclements, what's the magic /proc file to look in to find out timer resolution?

@aclements
Copy link
Member

grep resolution: /proc/timer_list

@rsc
Copy link
Contributor

rsc commented Jan 6, 2016 via email

@davecheney
Copy link
Contributor

@rsc from the canonical ppc64le machine

winton-01(~) % grep resolution: /proc/timer_list
  .resolution: 1 nsecs
  .resolution: 1 nsecs
  .resolution: 1 nsecs
  .resolution: 1 nsecs
  .resolution: 1 nsecs
  .resolution: 1 nsecs
  .resolution: 1 nsecs
  .resolution: 1 nsecs

@gopherbot
Copy link

CL https://golang.org/cl/18683 mentions this issue.

@golang golang locked and limited conversation to collaborators Feb 3, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants