-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Expose processes leveraged by BuildManager #11146
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
Conversation
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 know we also have some issues that have the error "Node # has exited unexpectedly", could a bit more information on the nodes help with that one too?
Tho goal of this PR is to help collect more relevant data with perfWatson on VS hangs - as important context might be in running out-of-proc MSBuild nodes, for which we are missing dumps. |
Fixes #11051
Context
For various hangs detection we need worker processes dumps. Let's unblock VS perf team in enabling automatic collection of worker processes dumps.
Testing
No tests provided.
This is best effort, point in time functionality, that should be used so
FYI @davkean