-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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 "invalid argument" on dragonfly-amd64 #50716
Comments
Is this a new test? Has it happened before? The /tmp mount point in the Gobuilder is tmpfs btw. |
This test is not new — see the above links for the failures in the dashboard logs. I see one failure this week, two toward the end of last year, and one from 2019 — so this looks like it used to be a somewhat rare race and is now a more common one (possibly due to scheduling effects from the GC pacing changes in Go 1.18).
|
Ok, we'll see what we can find out. Thanks for reporting! |
There has been some work that could probably fix this issue, but it's in current master: https://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/e91c5b2636e1fdd0d9e5170f24e5e39987211a49 whereas the gobuilder is running an older kernel (October, 2021). If I understood correctly, you prefer that we don't upgrade it yet. |
Yeah, since we can mitigate this particular failure with a test-skip it's probably better to hold off on upgrading until after the Go 1.18 release. (That way if the system upgrade introduces any other test failures we can diagnose them independent of any further changes in the Go 1.18 release itself.) |
Fine for me. Let's keep this issue opened and let me know when I can do the upgrade. |
This issue is currently labeled as early-in-cycle for Go 1.19. |
Can I upgrade the builder already? |
Yes, now would be a great time! 😃 |
Done! :) |
Looks like that did the trick!
[no results] |
Change https://go.dev/cl/402155 mentions this issue: |
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>
greplogs --dashboard -md -l -e 'FAIL: TestRemoveAllRace.*\n( .*\n)* .*: invalid argument'
2022-01-19T20:07:20-d1640d8/dragonfly-amd64
2021-12-02T18:02:46-c5c1955/dragonfly-amd64
2021-11-23T21:59:51-1ac45e0/dragonfly-amd64
2019-08-28T02:29:25-731e6fc/dragonfly-amd64
The test is here:
https://cs.opensource.google/go/go/+/master:src/os/os_test.go;l=2385-2418;drc=c8861432b84157363c84220e6ed71180531bf2b4
The
readdirent
part of that error message appears to come from here:https://cs.opensource.google/go/go/+/master:src/os/dir_unix.go;l=73;drc=2580d0e08d5e9f979b943758d3c49877fb2324cb
@tuxillo, any idea what might be causing this?
The text was updated successfully, but these errors were encountered: