Disable more flaky FSW tests for Windows #105638
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Tagging subscribers to this area: @dotnet/area-system-io |
jakobbotsch
approved these changes
Jul 29, 2024
This was referenced Jul 29, 2024
|
/ba-g DeadLetter is not caused by this change.. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Continuation of #105254.
Disabling tests more aggressively to unblock clean CI.
Tests excluded were testing functionality without using
ReadDirectoryChangesW, except for some that were not using theExpectEventinfrastructure in FileSystemWatcherTest.cs which haven't failed, I left those to see if the failures are somewhat related to test errors rather than flakyness.