-
Notifications
You must be signed in to change notification settings - Fork 4.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
[Test Failure] System.IO.Tests.InternalBufferSizeTests.FileSystemWatcher_InternalBufferSize #103753
Comments
Tagging subscribers to this area: @dotnet/area-system-io |
AFAIK this cod was not touched for months if not years, I have no idea why it suddenly started failing. @jozkee any ideas? |
Notes --started 6/19. Windows only both 32 and 64 bit. Apparently no relevant changes in IO or interop stuff. Test is expecting error event from the OS for particularly large buffer.
Guess: wild guess OS patched? Or IO hardware upgraded? Try updating the 10x multiplier. Aside: comments seem to suggest FILE_NOTIFY_INFORMATION is runtime/src/libraries/System.IO.FileSystem.Watcher/tests/FileSystemWatcher.InternalBufferSize.cs Lines 34 to 36 in e1f98a1
|
Failed in: runtime-coreclr crossgen2 20240622.1 Failed tests:
Error message:
Stack trace:
|
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=713266
Build error leg or test failing: System.IO.Tests.InternalBufferSizeTests.FileSystemWatcher_InternalBufferSize
Pull request: https://github.com/dotnet/runtime.git/pull/103720
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=713266
Error message validated:
[System.IO.Tests.InternalBufferSizeTests.FileSystemWatcher_InternalBufferSize Did not observe an error event within 500ms and 3 attempts.
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 6/20/2024 11:08:40 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: