-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Make bootstrap failures easier to debug #63236
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
Before bootstrap failures would occur in a target after `CoreCompile`. These failures were then repeated for all subsequent `Compilation` events that occurred after. In certain cases it made it hard to track down which compile event actually hit the error. Now it's very straight forward. This has the added bonus that the build fails fast when this happens vs. continuing on and making the log files even bigger.
|
@dotnet/roslyn-compiler PTAL. Making bootstrap failures easier to debug by failing compilation fast when possible. |
333fred
left a comment
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 (commit 2). I think it would also be good to check in a small doc to docs/Compilers about how you see this log.
That is a good idea. I will work on that. |
| // See the LICENSE file in the project root for more information. | ||
|
|
||
| #if !BOOTSTRAP | ||
| #if BOOTSTRAP |
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.
You didn't want the squirrel?
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.
Already have it 😄
Before bootstrap failures would occur in a target after
CoreCompile.These failures were then repeated for all subsequent
Compilationevents that occurred after. In certain cases it made it hard to track
down which compile event actually hit the error. Now it's very straight
forward.
This has the added bonus that the build fails fast when this happens vs.
continuing on and making the log files even bigger.