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: TestTraceStressStartStop fails on linux, windows sometimes #11953

Closed
davecheney opened this issue Jul 30, 2015 · 8 comments
Closed

runtime/trace: TestTraceStressStartStop fails on linux, windows sometimes #11953

davecheney opened this issue Jul 30, 2015 · 8 comments
Labels
FrozenDueToAge
Milestone
Go1.5

Comments

@davecheney
Copy link
Contributor 

--- FAIL: TestTraceStressStartStop (0.77s)
    trace_test.go:345: failed to parse trace: g 5 is not runnable before start (offset 445, time 250878)
FAIL
FAIL    runtime/trace   11.980s

Is unreliable, recent failures are

http://build.golang.org/log/58a391ca5363fd33fd4e8e86220fff2a04939645 (linux/arm64)

http://build.golang.org/log/e45ad86f06f071d19908771a74c89ac037af8479 (solaris/amd64)

--- FAIL: TestTrace (0.01s)
    trace_test.go:60: failed to parse trace: EvFrequency contains invalid frequency -214366821 at offset 0x12f
--- FAIL: TestTraceStressStartStop (0.10s)
    trace_test.go:345: failed to parse trace: EvFrequency contains invalid frequency -14474340013 at offset 0x3b4
FAIL
FAIL    runtime/trace   8.003s
@davecheney davecheney added this to the Go1.5 milestone Jul 30, 2015
@ianlancetaylor
Copy link
Contributor

CC @dvyukov @rsc

@rsc
Copy link
Contributor

rsc commented Jul 30, 2015

The solaris/amd64 one is fixed by ca6f7e4.
The linux/arm64 is more worrisome. That's not supposed to happen anymore.
It's possible there is something we don't understand that isn't right still.

@rsc rsc changed the title runtime/trace: TestTraceStressStartStop unreliable runtime/trace: TestTraceStressStartStop fails on linux/arm64 sometimes Jul 30, 2015
@davecheney
Copy link
Contributor Author

Just saw a failure on linux/386

http://build.golang.org/log/62b62b40de512697395a90784f6ba8865b5e2a80

--- FAIL: TestTraceStressStartStop (0.13s)
    trace_test.go:345: failed to parse trace: g 5 is not runnable before start (offset 2104, time 6810862)
FAIL
FAIL    runtime/trace   2.097s

@davecheney
Copy link
Contributor Author

And just now with darwin/amd64

http://build.golang.org/log/2d4c33d355892176fa11d9869948c8288ca363ad

--- FAIL: TestTraceStressStartStop (0.03s)
    trace_test.go:345: failed to parse trace: g 5 is not runnable before start (offset 1759, time 94953)
FAIL
FAIL    runtime/trace   1.775s

@dvyukov
Copy link
Member

dvyukov commented Jul 31, 2015

It happens on linux/amd64 machine pretty frequently:

814 runs so far, 5 failures
--- FAIL: TestTraceStressStartStop (0.18s)
trace_test.go:345: failed to parse trace: g 19 is not runnable before start (offset 31, time 142217)

On fde3926 (just before "runtime/trace: record event sequence numbers explicitly") no failures in 2838 runs. So it is broken by some recent changes.

@mikioh mikioh changed the title runtime/trace: TestTraceStressStartStop fails on linux/arm64 sometimes runtime/trace: TestTraceStressStartStop fails on linux, windows sometimes Aug 3, 2015
@mikioh
Copy link
Contributor

mikioh commented Aug 3, 2015

And windows: http://build.golang.org/log/4dfe01b46041cdbbce4a130f91ac970784c160ac

@mikioh
Copy link
Contributor

mikioh commented Aug 4, 2015

And freebsd: http://build.golang.org/log/a50b2f32d22e59a16a0943e6cd870daaf6adbeb9

@gopherbot
Copy link

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

@rsc rsc closed this as completed in 26baed6 Aug 6, 2015
@adg adg mentioned this issue Aug 10, 2015
Closed
@golang golang locked and limited conversation to collaborators Aug 5, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1.5
Development

No branches or pull requests
6 participants
@davecheney @mikioh @rsc @dvyukov @ianlancetaylor @gopherbot