Skip to content

runtime: TestCgoCCodeSIGPROF failures with SIGQUIT #41036

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 Aug 25, 2020 · 7 comments
Closed

runtime: TestCgoCCodeSIGPROF failures with SIGQUIT #41036

bcmills opened this issue Aug 25, 2020 · 7 comments
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. okay-after-beta1 Used by release team to mark a release-blocker issue as okay to resolve either before or after beta1 release-blocker
Milestone
Go1.19

Comments

@bcmills
Copy link
Contributor

bcmills commented Aug 25, 2020

2020-08-25T20:04:27-8381408/openbsd-amd64-64

See also #38333.
@bcmills bcmills added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Aug 25, 2020
@bcmills bcmills added this to the Backlog milestone Aug 25, 2020
@bcmills
Copy link
Contributor Author

bcmills commented Aug 25, 2020

CC @ianlancetaylor @aclements

@bcmills
Copy link
Contributor Author

bcmills commented Mar 17, 2022 •
edited
Loading

https://storage.googleapis.com/go-build-log/cd187ecc/linux-arm-aws_8ef98ffa.log (a linux-amd64-aws TryBot)

(CC @golang/runtime)

@bcmills bcmills modified the milestones: Backlog, Go1.19 Mar 17, 2022
@bcmills bcmills changed the title runtime: TestCgoCCodeSIGPROF failure due to SIGQUIT on openbsd-amd64-64 builder runtime: TestCgoCCodeSIGPROF failures due to SIGQUIT Mar 17, 2022
@bcmills bcmills changed the title runtime: TestCgoCCodeSIGPROF failures due to SIGQUIT runtime: TestCgoCCodeSIGPROF failures with SIGQUIT Mar 17, 2022
@cherrymui
Copy link
Member

Is there any new failure for this? Thanks.

@bcmills
Copy link
Contributor Author

bcmills commented May 18, 2022

Looks like the last one on the dashboard was 2021, and that one had a different stack (not in mstart1). 🤔

greplogs -l -e 'FAIL: TestCgoCCodeSIGPROF .*(?:\n[ ]{4}.*)*SIGQUIT'
2021-09-15T03:29:41-b26d325/linux-ppc64le-power9osu
2020-08-25T20:04:27-8381408/openbsd-amd64-64

@mknyszek
Copy link
Contributor

Since this is a test failure and unlikely to impact beta users, I'm going to mark this as okay-after-beta1.

@mknyszek mknyszek added the okay-after-beta1 Used by release team to mark a release-blocker issue as okay to resolve either before or after beta1 label May 25, 2022
@cherrymui
Copy link
Member

It seems the last failure is 2022-01-05T21:11:50-88cafe0/freebsd-arm64-dmgk
If there is no more failure maybe we can close this? (We can reopen if there is any new failure.)

@prattmic
Copy link
Member

prattmic commented Jun 9, 2022

It seems the last failure is 2022-01-05T21:11:50-88cafe0/freebsd-arm64-dmgk

This looks like it is TestGoroutineParallelism2. TestCgoCCodeSIGPROF is just waiting behind t.Parallel.

The last case I see is the one @bcmills listed.

greplogs --dashboard -md -l -e "(?s)FAIL: TestCgoCCodeSIGPROF.*SIGQUIT"
2021-09-15T03:29:41-b26d325/linux-ppc64le-power9osu

@prattmic prattmic closed this as completed Jun 9, 2022
Repository owner moved this from Todo to Done in Go Compiler / Runtime Jun 9, 2022
@prattmic prattmic closed this as not planned Won't fix, can't repro, duplicate, stale Jun 9, 2022
@golang golang locked and limited conversation to collaborators Jun 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. okay-after-beta1 Used by release team to mark a release-blocker issue as okay to resolve either before or after beta1 release-blocker
Projects
None yet
Milestone
Go1.19
Development

No branches or pull requests
5 participants
@mknyszek @prattmic @bcmills @gopherbot @cherrymui