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: TestCgoTracebackSigpanic failures #57595

Closed
gopherbot opened this issue Jan 4, 2023 · 5 comments
Closed

runtime: TestCgoTracebackSigpanic failures #57595

gopherbot opened this issue Jan 4, 2023 · 5 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. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone

Comments

@gopherbot
Copy link

gopherbot commented Jan 4, 2023

#!watchflakes
post <- pkg == "runtime" && test == "TestCgoTracebackSigpanic" && `runtime.sigpanic`

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestCgoTracebackSigpanic (34.57s)
    crash_test.go:58: /tmp/gobuilder-mips64/tmp/go-build3666441113/testprogcgo.exe TracebackSigpanic: exit status 2
    crash_cgo_test.go:518: 
    crash_cgo_test.go:521: did not see "runtime.sigpanic" in output

watchflakes

@gopherbot gopherbot added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. compiler/runtime Issues related to the Go compiler and/or runtime. labels Jan 4, 2023
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestCgoTracebackSigpanic"
2022-11-17 13:46 linux-mips-rtrk go@bed970b3 runtime.TestCgoTracebackSigpanic (log)
--- FAIL: TestCgoTracebackSigpanic (34.57s)
    crash_test.go:58: /tmp/gobuilder-mips64/tmp/go-build3666441113/testprogcgo.exe TracebackSigpanic: exit status 2
    crash_cgo_test.go:518: 
    crash_cgo_test.go:521: did not see "runtime.sigpanic" in output
2022-11-18 23:57 openbsd-386-71 go@04d6aa65 runtime.TestCgoTracebackSigpanic (log)
--- FAIL: TestCgoTracebackSigpanic (0.00s)
    crash_test.go:58: /tmp/workdir/tmp/go-build3123997662/testprogcgo.exe TracebackSigpanic failed to start: context deadline exceeded
2022-12-16 17:12 openbsd-amd64-71 go@f4b42f5c runtime.TestCgoTracebackSigpanic (log)
--- FAIL: TestCgoTracebackSigpanic (0.00s)
    crash_test.go:58: /tmp/workdir/tmp/go-build3915581810/testprogcgo.exe TracebackSigpanic failed to start: context deadline exceeded

watchflakes

@bcmills
Copy link
Contributor

bcmills commented Jan 6, 2023

The latter two look like #57585. Not sure about the linux-mips-rtrk failure.

@mknyszek
Copy link
Contributor

Given that the OpenBSD failures look unrelated to the linux/mips failures, and there's only been one linux/mips failure, this looks like a mips-specific flake. We should wait for it to reproduce, probably.

I updated the watchflakes expression to be more specific to the linux/mips failure.

CC @golang/mips

@mknyszek mknyszek added arch-mips WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. labels Jan 18, 2023
@mknyszek mknyszek added this to the Backlog milestone Jan 18, 2023
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestCgoTracebackSigpanic" && `runtime.sigpanic`
2023-01-26 07:17 darwin-amd64-10_15 go@cea70301 runtime.TestCgoTracebackSigpanic (log)
--- FAIL: TestCgoTracebackSigpanic (0.06s)
    crash_test.go:58: /tmp/buildlet/tmp/go-build4119296738/testprogcgo.exe TracebackSigpanic: signal: segmentation fault
    crash_cgo_test.go:520: 
    crash_cgo_test.go:523: did not see "runtime.sigpanic" in output
2023-01-26 07:17 darwin-amd64-11_0 go@cea70301 runtime.TestCgoTracebackSigpanic (log)
--- FAIL: TestCgoTracebackSigpanic (0.04s)
    crash_test.go:58: /tmp/buildlet/tmp/go-build2556092564/testprogcgo.exe TracebackSigpanic: signal: segmentation fault
    crash_cgo_test.go:520: 
    crash_cgo_test.go:523: did not see "runtime.sigpanic" in output
2023-01-26 10:15 darwin-amd64-10_15 go@4df10fba runtime.TestCgoTracebackSigpanic (log)
--- FAIL: TestCgoTracebackSigpanic (0.07s)
    crash_test.go:58: /tmp/buildlet/tmp/go-build1310876794/testprogcgo.exe TracebackSigpanic: signal: segmentation fault
    crash_cgo_test.go:520: 
    crash_cgo_test.go:523: did not see "runtime.sigpanic" in output
2023-01-26 10:15 darwin-amd64-11_0 go@4df10fba runtime.TestCgoTracebackSigpanic (log)
--- FAIL: TestCgoTracebackSigpanic (0.09s)
    crash_test.go:58: /tmp/buildlet/tmp/go-build4292740019/testprogcgo.exe TracebackSigpanic: signal: segmentation fault
    crash_cgo_test.go:520: 
    crash_cgo_test.go:523: did not see "runtime.sigpanic" in output

watchflakes

@seankhliao seankhliao added WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. and removed WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. labels Sep 18, 2023
@gopherbot
Copy link
Author

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

@gopherbot gopherbot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
Status: Done
Development

No branches or pull requests

4 participants