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
{
"ErrorMessage": "Binary log option was specified but MSBuild will be skipped because running just csc is enough",
"ErrorPattern": "",
"BuildRetry": true,
"ExcludeConsoleLog": false
}
Details
Multiple dotnet run file-mode tests that use cscOnly: True with -bl fail because they expect the output to contain the warning:
Warning: Binary log option was specified but MSBuild will be skipped because running just csc is enough. Specify '--no-cache' to force full build.
But the warning is not emitted, causing assertion failures.
Expected string to be the same string because Command did not output with Expected Output.
Expected: Warning: Binary log option was specified but MSBuild will be skipped because running just csc is enough. Specify '--no-cache' to force full build.
v1
Sample error (LaunchProfile test):
Expected string "Using launch settings from ...\launchSettings.json...
Hello from Program
Message: 'TestProfileMessage1'" to contain "Warning: Binary log option was specified but MSBuild will be skipped because running just csc is enough. Specify '--no-cache' to force full build.
Build: 🔎https://dev.azure.com/dnceng-public/public/_build/results?buildId=1378681 Error message validated:[Binary log option was specified but MSBuild will be skipped because running just csc is enough] Result validation: ✅ Known issue matched with the provided build. Validation performed at: 4/14/2026 9:13:57 PM UTC
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1378681
Build error leg or test failing: dotnet.Tests.dll.20, dotnet.Tests.dll.21, dotnet.Tests.dll.11
Pull request: #53635
Error Message
{ "ErrorMessage": "Binary log option was specified but MSBuild will be skipped because running just csc is enough", "ErrorPattern": "", "BuildRetry": true, "ExcludeConsoleLog": false }Details
Multiple
dotnet runfile-mode tests that usecscOnly: Truewith-blfail because they expect the output to contain the warning:But the warning is not emitted, causing assertion failures.
Affected tests:
Microsoft.DotNet.Cli.Run.Tests.RunFileTests_BuildOptions.WorkingDirectory(cscOnly: True)Microsoft.DotNet.Cli.Run.Tests.RunFileTests_CscOnlyAndApi.CscOnlyMicrosoft.DotNet.Cli.Run.Tests.RunFileTests_BuildCommands.LaunchProfile(cscOnly: True, relativePath: "Properties/launchSettings.json")Reproduces on main — confirmed in builds:
Sample error (WorkingDirectory test):
Sample error (LaunchProfile test):
Sample logs:
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1378681
Error message validated:
[Binary log option was specified but MSBuild will be skipped because running just csc is enough]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 4/14/2026 9:13:57 PM UTC
Report
Summary