Skip to content

runtime: TestDebugCall* flaky on android-amd64-emu #32985

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.

Sign up for GitHub

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
Closed
bcmills opened this issue Jul 8, 2019 · 11 comments
Closed

runtime: TestDebugCall* flaky on android-amd64-emu #32985

bcmills opened this issue Jul 8, 2019 · 11 comments
Labels
FrozenDueToAge mobile Android, iOS, and x/mobile NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Backlog

Comments

@bcmills
Copy link
Contributor

bcmills commented Jul 8, 2019

From the android-amd64-emu builder (https://build.golang.org/log/9cf7d64a00c151574d96c45a0b6e50358b527085):

##### GOMAXPROCS=2 runtime -cpu=1,2,4 -quick
--- FAIL: TestDebugCallPanic (0.01s)
    debug_test.go:244: executing on Go runtime stack
FAIL
exitcode=1FAIL	runtime	31.768s

CC @aclements @mknyszek
@bcmills bcmills added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jul 8, 2019
@bcmills bcmills added this to the Go1.13 milestone Jul 8, 2019
@andybons andybons modified the milestones: Go1.13, Go1.14 Jul 8, 2019
@bcmills
Copy link
Contributor Author

bcmills commented Jul 18, 2019

A very similar failure on android-amd64-emu in TestDebugCallGrowStack (https://build.golang.org/log/ee79c59d8a212e1461c433e52ff9427e44c2fad5):

##### GOMAXPROCS=2 runtime -cpu=1,2,4 -quick
--- FAIL: TestDebugCallGrowStack (0.00s)
    debug_test.go:183: executing on Go runtime stack
FAIL
exitcode=1FAIL	runtime	26.259s

@bcmills bcmills changed the title runtime: TestDebugCallPanic flake runtime: TestDebugCall* flaky on android-amd64-emu Jul 18, 2019
@bcmills bcmills added the mobile Android, iOS, and x/mobile label Jul 18, 2019
@bcmills
Copy link
Contributor Author

bcmills commented Aug 28, 2019

android-amd64-emu again: https://storage.googleapis.com/go-build-log/d068bbe4/android-amd64-emu_34b91ac9.log

@mvdan
Copy link
Member

mvdan commented Aug 29, 2019

Perhaps related? #33944

@bcmills
Copy link
Contributor Author

bcmills commented Sep 26, 2019

android-amd64-emu again: https://build.golang.org/log/96ce0d1b4decbb7edcdb2fc9e25da255d50638bb

@rsc rsc modified the milestones: Go1.14, Backlog Oct 9, 2019
@bcmills
Copy link
Contributor Author

bcmills commented Oct 31, 2019

android-amd64-emu again:
https://storage.googleapis.com/go-build-log/a75e00b3/android-amd64-emu_b51c7469.log

CC @aclements @cherrymui @danscales @mknyszek

@gopherbot
Copy link
Contributor

Change https://golang.org/cl/205248 mentions this issue: runtime: sleep a bit when waiting for running debug call goroutine

@bcmills bcmills mentioned this issue Nov 8, 2019
Closed
@bcmills
Copy link
Contributor Author

bcmills commented Nov 8, 2019

android-amd64-emu again: https://storage.googleapis.com/go-build-log/af0f6d56/android-amd64-emu_efb37c55.log

@gopherbot
Copy link
Contributor

Change https://golang.org/cl/206138 mentions this issue: runtime: skip TestDebugCall* on android-amd64-emu builder

@bcmills
Copy link
Contributor Author

bcmills commented Nov 18, 2019 •
edited
Loading

Still flaky:
https://build.golang.org/log/ba8d32ad60909355a4990a6a8f232695c42a7bc7

--- FAIL: TestDebugCallPanic (0.01s)
    debug_test.go:244: call from within the Go runtime
FAIL
exitcode=1FAIL	runtime	22.775s

@bcmills bcmills reopened this Nov 18, 2019
@ianlancetaylor
Copy link
Contributor

That's a different, albeit related, problem. Will send a CL.

@gopherbot
Copy link
Contributor

Change https://golang.org/cl/207620 mentions this issue: runtime: treat call from runtime as transient in TestDebugCall

@golang golang locked and limited conversation to collaborators Dec 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge mobile Android, iOS, and x/mobile NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
6 participants
@rsc @andybons @ianlancetaylor @mvdan @bcmills @gopherbot