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

internal/trace: TestTraceCPUProfile/Stress failures #70883

Open
gopherbot opened this issue Dec 17, 2024 · 1 comment
Open

internal/trace: TestTraceCPUProfile/Stress failures #70883

gopherbot opened this issue Dec 17, 2024 · 1 comment
Assignees
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@gopherbot
Copy link
Contributor

#!watchflakes
default <- pkg == "internal/trace" && test == "TestTraceCPUProfile/Stress"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestTraceCPUProfile/Stress
    reader_test.go:112: unexpected error while reading the trace: inconsistent status for goroutine 4: old Runnable vs. new Waiting
    trace_test.go:627: found bad trace; dumping to test log...
    trace_test.go:638: Trace Go1.23
        EventBatch gen=1 m=18446744073709551615 time=4827905708 size=5
        Frequency freq=15625000
        EventBatch gen=1 m=76763 time=4827904561 size=144
        ProcStatus dt=69 p=0 pstatus=1
        GoStatus dt=3 g=1 m=76763 gstatus=2
        ProcsChange dt=52 procs_value=8 stack=1
...
        String id=74
        	data="runtime.chanrecv1"
        String id=75
        	data="runtime.(*wakeableSleep).sleep"
        String id=76
        	data="runtime.traceStartReadCPU.func1"
        String id=77
        	data="/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/tracecpu.go"
        
--- FAIL: TestTraceCPUProfile/Stress (3.61s)

watchflakes

@gopherbot gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Dec 17, 2024
@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "internal/trace" && test == "TestTraceCPUProfile/Stress"
2024-12-17 16:05 gotip-linux-arm64-longtest go@31e50af5 internal/trace.TestTraceCPUProfile/Stress (log)
=== RUN   TestTraceCPUProfile/Stress
    reader_test.go:112: unexpected error while reading the trace: inconsistent status for goroutine 4: old Runnable vs. new Waiting
    trace_test.go:627: found bad trace; dumping to test log...
    trace_test.go:638: Trace Go1.23
        EventBatch gen=1 m=18446744073709551615 time=4827905708 size=5
        Frequency freq=15625000
        EventBatch gen=1 m=76763 time=4827904561 size=144
        ProcStatus dt=69 p=0 pstatus=1
        GoStatus dt=3 g=1 m=76763 gstatus=2
        ProcsChange dt=52 procs_value=8 stack=1
...
        String id=74
        	data="runtime.chanrecv1"
        String id=75
        	data="runtime.(*wakeableSleep).sleep"
        String id=76
        	data="runtime.traceStartReadCPU.func1"
        String id=77
        	data="/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/tracecpu.go"
        
--- FAIL: TestTraceCPUProfile/Stress (3.61s)

watchflakes

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Dec 17, 2024
@mknyszek mknyszek self-assigned this Dec 18, 2024
@mknyszek mknyszek added this to the Go1.24 milestone Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Status: No status
Development

No branches or pull requests

2 participants