-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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: TestCPUProfileWithFork is flaky #18349
Comments
Thanks for pulling this out of the other issue. I'm not sure what is happening here. The test was killed because it ran for more than 4 minutes. When I run the test with Can you recreate this at all? Do you have any FUSE file systems mounted (I'm looking at #11155)? |
I do indeed have a FUSE filesystem mounted, but I don't think the I saw several flakes yesterday, but am unable to reproduce one today. Pardon my ignorance, but I can't seem to figure out how to run individual standard-library tests in the correct environment. ( |
go test generally takes a package, not a file. The file support is very limited and weird, and probably doesn't work for the standard library.
|
Found a command-line that seems to run the test, but it's not reproducing the failure:
|
GOPATH="$GOROOT/src" is bogus. The GOPATH and GOROOT can't overlap. Some commands throw errors if they do. Probably "go test" should also. |
Ok, I think I've got my workspace in a more sane state: |
@bcmills, any update? |
I still haven't been able to reproduce the flakes I was seeing. |
(Extracted from a comment on #18332.)
TestCPUProfileWithFork is flaky for me using all.bash.
The text was updated successfully, but these errors were encountered: