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

runtime: TestGdbBacktrace failures #65176

Open
gopherbot opened this issue Jan 19, 2024 · 2 comments
Open

runtime: TestGdbBacktrace failures #65176

gopherbot opened this issue Jan 19, 2024 · 2 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. help wanted NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@gopherbot
Copy link

#!watchflakes
default <- pkg == "runtime" && test == "TestGdbBacktrace"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestGdbBacktrace
=== PAUSE TestGdbBacktrace
=== CONT  TestGdbBacktrace
    runtime-gdb_test.go:81: gdb version 12.1
    runtime-gdb_test.go:489: GDB command timed out after 5m21.961754265s: /usr/bin/gdb -nx -batch -iex add-auto-load-safe-path /home/swarming/.swarming/w/ir/x/w/goroot/src/runtime -ex set startup-with-shell off -ex break main.eee -ex run -ex backtrace -ex continue /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/a.exe
    runtime-gdb_test.go:494: gdb output:
        Loading Go Runtime support.
        Breakpoint 1 at 0x6979c: file /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go, line 17.
        [New LWP 370763]
        [New LWP 370764]
        [New LWP 370766]
        [New LWP 370767]
        
        Thread 1 "a.exe" hit Breakpoint 1, 0x000000000006979c in main.eee (~r0=<optimized out>) at /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go:17
        17	func eee() bool { return true }
        #0  0x000000000006979c in main.eee (~r0=<optimized out>) at /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go:17
        #1  0x000000000006978c in main.ddd (~r0=<optimized out>) at /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go:14
        #2  0x0000000000069750 in main.ccc (~r0=<optimized out>) at /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go:11
        #3  0x0000000000069720 in main.bbb (~r0=<optimized out>) at /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go:8
        #4  0x00000000000696f0 in main.aaa (~r0=<optimized out>) at /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go:5
        #5  0x00000000000697c8 in main.main () at /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go:22
        [LWP 370767 exited]
        [LWP 370766 exited]
        [LWP 370763 exited]
        [LWP 370761 exited]
    runtime-gdb_test.go:513: gdb exited with error: signal: killed
--- FAIL: TestGdbBacktrace (324.28s)

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 Jan 19, 2024
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "runtime" && test == "TestGdbBacktrace"
2024-01-17 20:26 gotip-linux-riscv64 go@8d04110c runtime.TestGdbBacktrace (log)
=== RUN   TestGdbBacktrace
=== PAUSE TestGdbBacktrace
=== CONT  TestGdbBacktrace
    runtime-gdb_test.go:81: gdb version 12.1
    runtime-gdb_test.go:489: GDB command timed out after 5m21.961754265s: /usr/bin/gdb -nx -batch -iex add-auto-load-safe-path /home/swarming/.swarming/w/ir/x/w/goroot/src/runtime -ex set startup-with-shell off -ex break main.eee -ex run -ex backtrace -ex continue /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/a.exe
    runtime-gdb_test.go:494: gdb output:
        Loading Go Runtime support.
        Breakpoint 1 at 0x6979c: file /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go, line 17.
        [New LWP 370763]
        [New LWP 370764]
        [New LWP 370766]
        [New LWP 370767]
        
        Thread 1 "a.exe" hit Breakpoint 1, 0x000000000006979c in main.eee (~r0=<optimized out>) at /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go:17
        17	func eee() bool { return true }
        #0  0x000000000006979c in main.eee (~r0=<optimized out>) at /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go:17
        #1  0x000000000006978c in main.ddd (~r0=<optimized out>) at /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go:14
        #2  0x0000000000069750 in main.ccc (~r0=<optimized out>) at /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go:11
        #3  0x0000000000069720 in main.bbb (~r0=<optimized out>) at /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go:8
        #4  0x00000000000696f0 in main.aaa (~r0=<optimized out>) at /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go:5
        #5  0x00000000000697c8 in main.main () at /home/swarming/.swarming/w/ir/x/t/TestGdbBacktrace964012512/001/main.go:22
        [LWP 370767 exited]
        [LWP 370766 exited]
        [LWP 370763 exited]
        [LWP 370761 exited]
    runtime-gdb_test.go:513: gdb exited with error: signal: killed
--- FAIL: TestGdbBacktrace (324.28s)

watchflakes

@mknyszek
Copy link
Contributor

In triage: maybe this is a hang in gdb? It wouldn't be that surprising. I think we need to wait for more.

CC @golang/riscv64

@mknyszek mknyszek added this to the Backlog milestone Jan 24, 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. help wanted 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