Uh oh!
There was an error while loading. Please reload this page.
Fix flaky FSW test - #103873
Conversation
BTW error case of too small InternalBufferSize is not being tested on non Windows (which may have different error behavior/limits) |
danmoseley
commented
Jun 23, 2024
Comment says "where filePath is the path to changed file relative to the path passed into ReadDirectoryChanges." .. but the math does not use the relative path. Small beans; will cause over estimate, increasing events. |
adamsitnik
left a comment
There was a problem hiding this comment.
LGTM, thank you for providing the fix @danmoseley !
danmoseley
commented
Jun 24, 2024
Can we run outer loop on this PR? It's just speculation that this will fix the test |
jozkee
commented
Jun 24, 2024
/azp list |
This comment was marked as off-topic.
This comment was marked as off-topic.
jozkee
commented
Jun 24, 2024
/azp run runtime-libraries-coreclr outerloop-windows |
|
Azure Pipelines successfully started running 1 pipeline(s). |
jozkee
commented
Jun 24, 2024
#103753 also mentions |
danmoseley
commented
Jun 24, 2024
Right, not really evidence that's related. Eg., it didn't start on the same day, it only happened once. |
danmoseley
commented
Jun 24, 2024
OK, Build Analysis is recognizing all failures, so this is good to merge if you're OK with that @jozkee |
jozkee
commented
Jun 9, 2025
/backport to release/8.0-staging |
Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/15537894547 |
Fix#103753
Test does not fail for me locally; making assumption that firing even more events will this will help avoid it failing elsewhere.