-
Notifications
You must be signed in to change notification settings - Fork 13
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
follow-up for dotnet-trace #304
Conversation
@nicrowe00 fyi, the trace files generated by the tool can be read using https://www.nuget.org/packages/Microsoft.Diagnostics.Tracing.TraceEvent/. There's an example in this blog post that shows how to use the library for reading a trace file: https://developers.redhat.com/blog/2019/12/23/tracing-net-core-applications. I'm ok with validating the output of the topN because that will read the trace to create a summary. |
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.
LGTM!
Rewriting a portion of the test for dotnet-trace, specifically dealing with the 'report' command. Instead of verifying that the report log file exists, the test now checks the output of the command to verify that a specific method is on the callstack. Signed-off-by: Niall Crowe <nicrowe@redhat.com>
Rewriting a portion of the test for dotnet-trace, specifically dealing with the 'report' command. Instead of verifying that the report log file exists, the test now checks the output of the command to verify that a specific method is on the callstack.