Repository navigation
Conversation
msbuild.exe builds on one node unless it gets -m, while the dotnet CLI passes -maxcpucount on its own. The MSBuild job's binlog shows 21.4 minutes on one node, 12.4 of them in Build. The win-x64 leg builds the same solution filter with dotnet build in 3 to 4.5 minutes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5796 +/- ##
=======================================
Coverage 76.13% 76.13%
=======================================
Files 528 528
Lines 19579 19579
Branches 3829 3829
=======================================
+ Hits 14906 14907 +1
+ Misses 3791 3790 -1
Partials 882 882 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
With -m, msbuild.exe also reuses its worker nodes and leaves them running after the build. Nothing later in the job uses them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The MSBuild job runs
msbuild.exewithout-m, so it builds the whole Windows solution filter on a single node. ThedotnetCLI passes-maxcpucounton its own, which is why the .NET legs already use every core.From the job's binlog on #5793:
msbuildran 21.4 minutes on 1 node: Restore 8.2, Build 12.4 and Pack 0.3.dotnet workload listcalls fromOnlyTargetInstalledWorkloadsinDirectory.Build.targets, one per project and target framework, all waiting on each other..NET (win-x64)leg builds the same filter withdotnet buildin 3 to 4.5 minutes.#4300 added this job to catch build breaks that only happen in Visual Studio, like
RuntimeInformation.RuntimeIdentifierfailing under .NET Framework MSBuild. With-mit's still the same MSBuild building the same projects, and Visual Studio builds in parallel too.The job took 22.8 to 29.5 minutes on the last 6 runs, so with the other open CI PRs it would be the next job to hold up the build workflow.
-malso turns on node reuse, which leaves MSBuild's worker processes running after the step. Nothing later in the job uses them, so the command passes-nr:falsetoo.Measured on the first run, against 3 runs from the same evening without
-m:-mRun MSBuildstepSentry.Samples.Mauifor Android on a single node, which ci: build the app samples in their own job #5783 moves out of this solution filter.C:. ci: install .NET and NuGet packages on a faster drive on Windows #5782 now moves them next to the workspace for this job too, and on its own run the step took 14.7 minutes.-mfrom the same evening: 44 warnings with the same codes, no errors, and the same 49 packages.#skip-changelog