Get better assert failure in flaky FlushAsync_ThrowsIfWriterReaderWithException test#57081
Merged
Get better assert failure in flaky FlushAsync_ThrowsIfWriterReaderWithException test#57081
Conversation
|
Tagging subscribers to this area: @dotnet/area-system-io Issue DetailsThis should give us a test failure like the following: Instead of I'm hoping this helps with debugging.
|
Member
Author
|
Given that #55446 has been merged, will I see any new failures? I don't see failures since 7/10, but I'm struggling to adjust the date range the Azure Pipelines test history UI, so I could be missing something. |
This file contains hidden or 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
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.
This should give us a test failure like the following:
Instead of
I'm hoping this helps with debugging.
This is to help investigate #55435