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

Jump to bottom

sync: TestMutexFairness failure on openbsd-arm64-jsing #56586

Open
gopherbot opened this issue Nov 4, 2022 · 4 comments
Open

sync: TestMutexFairness failure on openbsd-arm64-jsing #56586

gopherbot opened this issue Nov 4, 2022 · 4 comments
Assignees
@qbit @4a6f656c
Labels
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.
Milestone
Backlog

Comments

@gopherbot
Copy link 

#!watchflakes
post <- pkg == "sync" && test == "TestMutexFairness"

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestMutexFairness (10.02s)
    mutex_test.go:227: can't acquire Mutex in 10 seconds

— 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 Nov 4, 2022
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
post <- pkg == "sync" && test == "TestMutexFairness"
2022-11-02 19:08 openbsd-arm64-jsing go@ca8b3192 sync.TestMutexFairness (log) 
--- FAIL: TestMutexFairness (10.02s)
    mutex_test.go:227: can't acquire Mutex in 10 seconds

— watchflakes

@bcmills
Copy link
Contributor

bcmills commented Nov 4, 2022 •
edited

See previously #53174 (attn @4a6f656c )

@bcmills bcmills changed the title sync: TestMutexFairness failures sync: TestMutexFairness failure on openbsd-arm64-jsing Nov 4, 2022
@mknyszek
Copy link
Contributor

mknyszek commented Nov 9, 2022

CC @golang/openbsd

@mknyszek
Copy link
Contributor

mknyszek commented Nov 9, 2022

I don't think this is going to be related to some wider e.g. runtime work because AFAIK there haven't been any significant changes to the scheduler or the way mutexes are implemented in recent memory. This might be a platform/machine specific flake.

@mknyszek mknyszek added this to the Backlog milestone Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@qbit qbit

@4a6f656c 4a6f656c

Labels
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.
Projects
Go Compiler / Runtime
Status: Todo
Test Flakes
Status: No status
Milestone
Backlog
Development

No branches or pull requests
5 participants
@qbit @mknyszek @bcmills @4a6f656c @gopherbot