-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Ensure all expected paths are logged on test failure #65666
Conversation
Tagging subscribers to this area: @dotnet/area-system-io Issue DetailsThe failure provided in #65601 is not very helpful:
Let's print all information in the exception message so we can move on with #65601 diagnostics.
|
src/libraries/System.IO.FileSystem.Watcher/tests/Utility/FileSystemWatcherTest.cs
Outdated
Show resolved
Hide resolved
} | ||
catch (Exception ex) | ||
{ | ||
_output?.WriteLine(ex.ToString()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These were saving the exception information out to the log file. That's not useful anymore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on the information provided in #65601 I don't think it's useful:
Not found: /var/folders/62/ftpn5pv523j8xsdw56s9jnp40000gs/T/Directory_Create_Tests_hsm4w3hg.os4/FileSystemWatcher_Directory_Create_InNestedDirectory_53_bb03705a/dir1
In value: String[] ["/var/folders/62/ftpn5pv523j8xsdw56s9jnp40000gs/T/D"...]
Since the exception was re-thrown anyway I don't see any benefits of keeping this logic. Am I missing something?
Co-authored-by: Stephen Toub <stoub@microsoft.com>
The failure provided in #65601 is not very helpful:
Let's print all information in the exception message so we can move on with #65601 diagnostics.