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.

Sign up for GitHub

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

Jump to bottom

runtime/trace: TestTraceSymbolize flaky on linux-386 #17238

Closed
cherrymui opened this issue Sep 26, 2016 · 4 comments
Closed

runtime/trace: TestTraceSymbolize flaky on linux-386 #17238

cherrymui opened this issue Sep 26, 2016 · 4 comments
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Go1.8

Comments

@cherrymui
Copy link
Member

Trybot failure on CL https://go-review.googlesource.com/c/29734/
https://storage.googleapis.com/go-build-log/c51bd259/linux-386_3c61fdbb.log
@quentinmit
Copy link
Contributor

/cc @aclements Can you run your flake finder?

@quentinmit quentinmit added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Oct 4, 2016
@quentinmit quentinmit added this to the Go1.8 milestone Oct 4, 2016
@aclements
Copy link
Member

$ greplogs -dashboard -e TestTraceSymbolize -e 'did not match' -md -l | tail
2016-03-13T23:34:31-d1341d6/linux-arm64-linaro
2016-04-04T05:23:18-02adfa0/openbsd-386-gce58
2016-04-14T18:35:09-24bd465/openbsd-386-gce58
2016-04-27T21:14:32-cbd7231/linux-amd64-clang
2016-05-05T19:15:38-fafd792/openbsd-amd64-gce58
2016-05-20T22:51:51-7ab698b/linux-amd64-sid
2016-06-29T23:59:41-51b08d5/linux-amd64-race
2016-07-02T00:40:40-519b469/freebsd-arm-paulzhol
2016-08-09T00:43:25-392bf3a/darwin-amd64-10_8
2016-09-09T22:50:41-1161a19/openbsd-amd64-gce58

$ greplogs -dashboard -e TestTraceSymbolize -e 'did not match' -l | findflakes -paths
First observed 1161a19 09 Sep 22:50 2016 (364 commits ago)
Last observed  1161a19 09 Sep 22:50 2016 (364 commits ago)
Isolated failure
Past failures:
  02adfa0 04 Apr 05:23 2016 to 392bf3a 09 Aug 00:43 2016
    0.60% failure probability (8 of 1161 commits)
  7758a94 09 Mar 00:18 2016 to d1341d6 13 Mar 23:34 2016
    1.0% failure probability (2 of 105 commits)
  5a0d9ef 14 Nov 13:12 2015 to 4feb47b 24 Feb 18:42 2016
    1.9% failure probability (19 of 972 commits)
  8acaacb 28 Aug 22:05 2015 to 8ee90fa 04 Nov 16:03 2015
    1.5% failure probability (10 of 607 commits)
  5e15e28 03 Aug 04:41 2015 (isolated failure)
  bd5ca22 29 Jul 22:32 2015 to ab714a7 30 Jul 15:47 2015
    100% failure probability (9 of 9 commits)
  ad84f84 23 Jul 17:49 2015 (isolated failure)
  751eef8 25 Jun 13:17 2015 (isolated failure)
  919fd24 10 Mar 14:46 2015 to d0eab03 10 Mar 15:04 2015
    100% failure probability (2 of 2 commits)

@rsc
Copy link
Contributor

rsc commented Oct 27, 2016

Pretty sure this is the miniscule sleeps in the test not being long enough. Will send a CL.

@gopherbot
Copy link

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

@golang golang locked and limited conversation to collaborators Oct 28, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Go1.8
Development

No branches or pull requests
5 participants
@rsc @quentinmit @aclements @gopherbot @cherrymui