-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
CI: Another macos FileWatching failure #46185
Comments
@vtjnash thoughts on what the expected behavior should be? |
If I'm reading the kernel source correctly, it does look like events should show up in order: https://github.com/apple/darwin-xnu/blob/2ff845c2e033bd0ff64b5b6aa6063a1f8f65aa32/bsd/vfs/vfs_fsevents.c. Though there's a userspace |
Another one (https://buildkite.com/julialang/julia-master/builds/14598#01827ba7-bbb0-4ff8-a462-5475b793a4f9):
|
I think the hypothesis that fseventsd is re-ordering events is pretty well validated at this point, and we'll just have to adjust the test or disable it on macos. |
maybe this is relevant dotnet/runtime#30415 |
Yeah, same issue. We can keep tracking this, but I think for CI purposes, we just need to turn off the test or make it robust to re-ordering. @gbaraldi want to take a crack at it? |
Sure, will see if I can get it to reproduce easier |
Recent failures julia/stdlib/FileWatching/test/runtests.jl Lines 189 to 191 in 36aab14
and https://buildkite.com/julialang/julia-master/builds/15032#0182d266-b194-4cf3-b0f4-c05eab8ac7e7 julia/stdlib/FileWatching/test/pidfile.jl Line 292 in 36aab14
This last one is interesting because it doesn't seem event related @Keno |
#46497 didn't entirely fix this, but should have avoided the CI issues now |
Same failures on aarch64-darwin. https://logs.nix.ci/?attempt_id=66e4325a-4d1f-40af-888f-fb276ed411d9&key=nixos%2Fnixpkgs.205584
|
Separate from #45982, we have another macos-specific FileWatching failure:
This looks a lot like #26725 in that we may be getting these events (or rather these events and the events from the previous loop) out-of-order. We should first determine if we should we expect the kernel to deliver these in order. If not, we should adjust the tests accordingly. If so, we should complain to Apple.
The text was updated successfully, but these errors were encountered: