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.

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

internal/trace: TestTraceCPUProfile/Stress failures [1.23 backport] #71147

Open
gopherbot opened this issue Jan 7, 2025 · 0 comments
Open

internal/trace: TestTraceCPUProfile/Stress failures [1.23 backport] #71147

gopherbot opened this issue Jan 7, 2025 · 0 comments
Labels
CherryPickCandidate Used during the release process for point releases compiler/runtime Issues related to the Go compiler and/or runtime.
Milestone
Go1.23.5

Comments

@gopherbot
Copy link
Contributor

@mknyszek requested issue #70883 to be considered for backport to the next 1.23 minor release.

@gopherbot Please open backport issues for Go 1.22 and Go 1.23.

This bug means a rare chance that the tracer will emit broken traces with no workaround. The fix is also small and concerns only tracer-related code. (It touches the scheduler, but the scheduler logic is left as-is.)
@gopherbot gopherbot added the CherryPickCandidate Used during the release process for point releases label Jan 7, 2025
@gopherbot gopherbot mentioned this issue Jan 7, 2025
Open
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jan 7, 2025
@gopherbot gopherbot added this to the Go1.23.5 milestone Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CherryPickCandidate Used during the release process for point releases compiler/runtime Issues related to the Go compiler and/or runtime.
Projects
None yet
Milestone
Go1.23.5
Development

No branches or pull requests
1 participant
@gopherbot