Skip to content

runtime: mayMoreStackPreempt tests flaky after stack frame CLs #54885

Closed
@prattmic

Description

@prattmic

greplogs --dashboard -md -l -e 'SignalInVDSO'

2022-09-05T21:39:28-4c1ca42/linux-386-longtest
2022-09-05T08:28:34-bd5595d/linux-386-longtest
2022-09-05T08:08:24-af7f417/linux-386-longtest
2022-09-05T08:08:18-4ad55cd/linux-386-longtest
2022-09-05T08:07:47-357b922/linux-386-longtest
2022-09-05T07:17:56-4e7e7ae/linux-386-longtest
2022-09-05T07:14:08-3fbcf05/linux-386-longtest
2022-09-04T04:17:04-535fe2b/linux-386-longtest
2022-09-03T18:21:45-a0f0582/linux-386-longtest
2022-09-03T15:45:36-f798dc6/linux-386-longtest
2022-09-02T19:22:26-0fda8b1/linux-386-longtest
2022-09-02T19:09:03-55ca6a2/linux-386-longtest
2022-09-02T19:08:56-b91e373/linux-386-longtest
2022-09-02T19:08:53-dbf442b/linux-386-longtest

##### maymorestack=mayMoreStackPreempt
--- FAIL: TestVDSO (0.43s)
    testenv.go:468: [/workdir/tmp/go-build2185756284/testprog.exe SignalInVDSO] exit status: signal: segmentation fault (core dumped)
    crash_test.go:144: output:
        
        
        wanted:
        success
FAIL
FAIL	runtime	95.198s
FAIL

The first failure occurred on https://go.dev/cl/424514. It is flaky, so it may not be precisely that CL at fault, but it seems likely that one of the stack frame CLs is to blame.

Metadata

Metadata

Assignees

Labels

FrozenDueToAgeNeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.compiler/runtimeIssues related to the Go compiler and/or runtime.release-blocker

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions