-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
os: TestRemoveAllRace failures with "directory not empty" on dragonfly-amd64 #52301
Comments
See previously #33403 (especially relevant because it was also reported on DragonFly). |
|
Change https://go.dev/cl/402155 mentions this issue: |
@bcmills seems like we should have a look at our unlinkat(2) implementation, right? |
Yep, looks like |
This test occasionally fails on the dragonfly-amd64 builder with "directory not empty". Since that is the only platform on which we observe these failures, and since the test had a different (and also invalid-looking) failure mode prior to this one (in #50716), we suspect that it is due to either a bug in the platform or a platform-specific Go bug. For #52301. Change-Id: Id36c499651b9c48e6b8b0107d01f73d2a7b6bab8 Reviewed-on: https://go-review.googlesource.com/c/go/+/402155 Run-TryBot: Bryan Mills <bcmills@google.com> Auto-Submit: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@google.com>
Moving to Backlog. Please comment if you disagree. Thanks. |
greplogs --dashboard -md -l -e 'FAIL: TestRemoveAllRace .*(?:\n .*)*directory not empty' --since=2022-01-01
2022-04-12T03:07:42-d4dbad5/dragonfly-amd64
2022-03-21T18:58:34-d8ce7ae/dragonfly-amd64
This failure mode seems to occur instead of the
invalid argument
failure mode observed in #50716 (attn @tuxillo).The text was updated successfully, but these errors were encountered: