You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Review our current policy of emitting MsBuild text-based logs and maximize the use of binlog files that contain much more complete information usable for investigating build issues.
Measure MsBuild performance w.r.t. emitting the text-based vs. binlog files;
Use the measurements to design which product / test build steps should newly produce binlog files in addition to or instead of the existing text logs without substantial performance degradation;
Review the design on the @dotnet/runtime-infrastructure alias;
Implement the design.
The text was updated successfully, but these errors were encountered:
Note that there's an API to playback the .binlog into a text log with any level of verbosity.
Also it's simple to write a console app that will read all the warnings/errors from the binlog and output them to a text log.
However note that reading a .binlog on Core is 10x slower than on Desktop because of this bug: #39233
Adding /bl does slow down your build, but not as much as adding a text log with diag verbosity.
My recommendation is to use /bl and no text logs, and generate text logs either via a little tool or on demand.
Also you can view binlogs online using https://live.msbuildlog.com so maybe integrating that into the CI somehow might also be interesting.
Update: we have found a workaround for the slowdown I mentioned when reading .binlogs. Just wrapping the GZipStream with a BufferedStream solves the issue.
Initial cost estimate: 2 weeks
Initial contacts: @trylek, @safern, @ViktorHofer
Review our current policy of emitting MsBuild text-based logs and maximize the use of binlog files that contain much more complete information usable for investigating build issues.
The text was updated successfully, but these errors were encountered: