-
Notifications
You must be signed in to change notification settings - Fork 4k
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
How to troubleshoot a build-time regression #67161
Conversation
docs/wiki/Troubleshooting-tips.md
Outdated
The file is written next to the compilation output and has a `.key` suffix. | ||
Comparing those files between slow and fast runs helps detect pertinent changes (new inputs, new references, etc). | ||
3. compiler server issue: | ||
Inspect the binary log (search for "Error:" and such). |
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.
💡 There is a predefined (example) search term in MSBuild Structured Log Viewer for $message CompilerServer failed
that I normally use for this.
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.
Good to know. Thanks!
@jaredpar @dotnet/roslyn-compiler for review. Thanks |
docs/wiki/Troubleshooting-tips.md
Outdated
Use `/p:Features=debug-determinism` to create an additional output file that documents all the inputs to a particular compilation. | ||
The file is written next to the compilation output and has a `.key` suffix. | ||
Comparing those files between slow and fast runs helps detect pertinent changes (new inputs, new references, etc). | ||
3. compiler server issue: |
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.
This would be #2 for me.
No description provided.