This repository has been archived by the owner on Dec 3, 2019. It is now read-only.
Pyflame can't profile its own test suite #114
Comments
eklitzke
added a commit
to eklitzke/pyflame
that referenced
this issue
Aug 9, 2017
eklitzke
added a commit
that referenced
this issue
Aug 9, 2017
akatrevorjay
added a commit
to akatrevorjay/pyflame
that referenced
this issue
Oct 6, 2017
* origin/master: fix SIGCHLD issue reported in uber-archive#122 tag 1.5.6 show supported ABIs in -v output handle EAGAIN during munmap(2) system call (uber-archive#118) tag v1.5.5, to fix a regression in trace mode fix handling child execs in traced processes, closes uber-archive#114 (uber-archive#117) disable i386 python 2.7 tests (uber-archive#116) use the more standard "make check" rather than "make test" . Get the Pyflame test suite to pass on i386 (uber-archive#112) release v1.5.3 Build Pyflame on i386 hosts. (uber-archive#110)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I wanted to Pyflame the Pyflame test suite, but Pyflame exited very early with a 0 status code. I haven't dug into this yet, but just from thinking about it my guess is that when Pyflame becomes the parent of the traced process it's somehow getting notifications from grandchild processes or something, and then the
waitid()loop thinks the traced process has exited. In any event, after building Pyflame the following command should not print profiling data until the test suite is actually done running:This is tangentially related to #67, if my
waitid()theory is true.The text was updated successfully, but these errors were encountered: