-
Notifications
You must be signed in to change notification settings - Fork 13.7k
Improve tracing in bootstrap #145261
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
Merged
Merged
Improve tracing in bootstrap #145261
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
e6dddcb
Store bootstrap tracing outputs to a unified directory
Kobzol c97b606
Store `latest` symlink to the latest tracing output directory
Kobzol f819729
Store Chrome step trace into the tracing directory
Kobzol aad5795
Use shorter command span label
Kobzol 3a115ba
Print step timings also when the stap starts to execute
Kobzol c846f7c
Replace `tracing_forest` with custom span formatting
Kobzol 1e14229
Create a span for each executed step
Kobzol 690c781
Remove ad-hoc print of executed/cached steps in verbose mode
Kobzol d403934
Remove manual `#[instrument]` annotations on steps
Kobzol 604c180
Move tracing setup to the `tracing` module
Kobzol c3682b2
Correctly show executed command name in Chrome trace
Kobzol b4a357f
Always profile commands and generate Chrome profile when tracing is e…
Kobzol f9a4588
Do not create a span for cached commands
Kobzol 12828f7
Create tracing directory symlink even during dry run
Kobzol 3e77562
Use `pretty_step_name` in `step_graph`
Kobzol a0306bf
Update debugging/profiling bootstrap page
Kobzol 6f584bc
Print created location of executed commands
Kobzol 0b8c6ad
Remove one dependency from tracing bootstrap build
Kobzol File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Remark: I wonder if we should suppress the e.g.
messages that interleave the tracing output, but this is fine
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.
I think that the interleaving is a feature, not a bug - you can then figure out where were the messages actually printed, in relation to how were the steps executed. That being said, we currently print these logs to stdout, but the tracing is printed to stderr, so the interleaving can be a bit non-deterministic.
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.
Right. That is fine.