Repository navigation
[Test Failure] System.IO.Tests.InternalBufferSizeTests.FileSystemWatcher_InternalBufferSize #103753
Description
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.
{
"ErrorMessage": ["System.IO.Tests.InternalBufferSizeTests.FileSystemWatcher_InternalBufferSize", "Did not observe an error event within 500ms and 3 attempts."] ,
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}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
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 13 | 58 | 58 |
Activity
dotnet-policy-service commentedon Jun 20, 2024
Tagging subscribers to this area: @dotnet/area-system-io
See info in area-owners.md if you want to be subscribed.
adamsitnik commentedon Jun 21, 2024
AFAIK this cod was not touched for months if not years, I have no idea why it suddenly started failing.
@jozkee any ideas?
danmoseley commentedon Jun 23, 2024
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.
Not clear where this comes from, and it doesn't convert WCHAR into bytes so it will over-estimate. But also seems 17 should be 12, see below. So it should divide by (12 + 2 * (file name length + 1))?
Guess: wild guess OS patched? Or IO hardware upgraded? Try updating the 10x multiplier.
Aside: comments seem to suggest FILE_NOTIFY_INFORMATION is
16 + 2 * (Path.GetFileName(file.Path).Length + 1)but the leading bytes appear to be 12 not 16 (3x DWORD). In either case that doesn't make 17.runtime/src/libraries/System.IO.FileSystem.Watcher/tests/FileSystemWatcher.InternalBufferSize.cs
Lines 34 to 36 in e1f98a1
v-wenyuxu commentedon Jun 24, 2024
Failed in: runtime-coreclr crossgen2 20240622.1
Failed tests:
Error message:
Stack trace:
ViveliDuCh commentedon Oct 21, 2026
Reopening for a recurrence on
release/8.0in #136200.System.IO.Tests.InternalBufferSizeTests.FileSystemWatcher_InternalBufferSize(setToHigherCapacity: False)net8.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.Client.OpenDid not observe an error event within 500ms and 3 attempts.The fix in #103873 is present in main and release/9.0 through release/11.0, but is missing from the failing release/8.0 SHA (
da8dbac37b3cb15798931a078672568e5553f85b). The attempted .NET 8 backport, #116432, encountered build errors and was closed unmerged. This recurrence needs a working .NET 8 backport of the test fix.Build Analysis did not classify this occurrence under this known issue because the issue was closed.