Embed diagnostics in binlog #182
Merged
+3
−0
Conversation
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
jaredpar
approved these changes
Apr 28, 2025
|
Btw, looks like I need someone else to merge this, I don't have merge permissions here |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
SourceBrowser emits compilation diagnostics into
diagnostics.txtfiles. Some can be seen directly like https://source.dot.net/Microsoft.CodeAnalysis/diagnostics.txt but others return 500 (they might be too long), e.g., https://source.dot.net/Microsoft.CodeAnalysis.CSharp/diagnostics.txt. By embedding the files into the binlog, we can inspect them from official CI builds at least.This should simplify diagnosing issues like #174.
Official build test run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2697195&view=results