feat: support uploading runtime trace files to slack #23
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 extends our existing infra to record runtime traces to actually upload the trace file to the message thread. This will help diagnose issues like microsoft/vscode#241640 (comment) and other runtime specific issues arising from the perf infra.
Following changes are made,
--runtime-traceoption is used, the trace file from the run that hasbestDurationin the current session will get uploaded to the slack message thread.Here is it in action,
TODO before deploying
file:writescope on the PerfBot App, need admin on VS Code repo to update and reinstall the application.--runtime-tracespecified when using this module from the perf bot.