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

Jump to bottom

runtime: TestSegv failures with unknown pc on linux-mips-rtrk #59029

Open
gopherbot opened this issue Mar 14, 2023 · 2 comments
Open

runtime: TestSegv failures with unknown pc on linux-mips-rtrk #59029

gopherbot opened this issue Mar 14, 2023 · 2 comments
Labels
arch-mips 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.

Comments

@gopherbot
Copy link

gopherbot commented Mar 14, 2023 •
edited by bcmills 

#!watchflakes
post <- pkg == "runtime" && test == "TestSegv" && goarch ~ `mips` && `unknown pc`

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/Segv (0.05s)
        crash_cgo_test.go:622: /tmp/gobuilder-mips64/tmp/go-build3665412076/testprogcgo.exe Segv: exit status 2
        crash_cgo_test.go:623: SIGSEGV: segmentation violation
            PC=0x77ed2ca4 m=4 sigcode=0

            r0   0x0	r1   0x1
            r2   0x0	r3   0x1
            r4   0x3	r5   0x7297ec88
            r6   0x0	r7   0x0
            r8   0x0	r9   0x0
            r10  0x0	r11  0x77e9b400
            r12  0x1	r13  0x70c00481
            r14  0x0	r15  0x8f
            r16  0x77f23afc	r17  0x7297ec88
            r18  0x6c42a0	r19  0x800000
            r20  0x48fdec	r21  0x77eed000
            r22  0x7297ed9c	r23  0xfffffff8
            r24  0xc	r25  0x77ed2c50
            r26  0x10	r27  0x0
            r28  0x77ef5020	r29  0x7297ebc8
            r30  0x800d00	r31  0x577b08
            pc   0x77ed2ca4	link 0x577b08
            lo   0x0	hi   0x0

        crash_cgo_test.go:654: unexpectedly saw "runtime: " in output

— 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 Mar 14, 2023
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestSegv"
2023-03-13 22:04 linux-mips-rtrk go@40a6e2da runtime.TestSegv (log) 
--- FAIL: TestSegv (0.00s)
    --- FAIL: TestSegv/Segv (0.05s)
        crash_cgo_test.go:622: /tmp/gobuilder-mips64/tmp/go-build3665412076/testprogcgo.exe Segv: exit status 2
        crash_cgo_test.go:623: SIGSEGV: segmentation violation
            PC=0x77ed2ca4 m=4 sigcode=0

            r0   0x0	r1   0x1
            r2   0x0	r3   0x1
            r4   0x3	r5   0x7297ec88
            r6   0x0	r7   0x0
            r8   0x0	r9   0x0
            r10  0x0	r11  0x77e9b400
            r12  0x1	r13  0x70c00481
            r14  0x0	r15  0x8f
            r16  0x77f23afc	r17  0x7297ec88
            r18  0x6c42a0	r19  0x800000
            r20  0x48fdec	r21  0x77eed000
            r22  0x7297ed9c	r23  0xfffffff8
            r24  0xc	r25  0x77ed2c50
            r26  0x10	r27  0x0
            r28  0x77ef5020	r29  0x7297ebc8
            r30  0x800d00	r31  0x577b08
            pc   0x77ed2ca4	link 0x577b08
            lo   0x0	hi   0x0

        crash_cgo_test.go:654: unexpectedly saw "runtime: " in output

— watchflakes

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Mar 14, 2023
@bcmills bcmills changed the title runtime: TestSegv failures runtime: TestSegv failures with unknown pc on linux-mips-rtrk Mar 14, 2023
@bcmills
Copy link
Member

bcmills commented Mar 14, 2023

(attn @golang/mips; CC @golang/runtime)

See also #52963.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
arch-mips 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
Go Compiler / Runtime
Status: No status
Test Flakes
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bcmills @gopherbot