dotnet / dotnet/sdk

Error treated as warning on dotnet sdk source build ->

Open
#45,104 0 comments 0 reactions 0 assignees View on GitHub
Area-Infrastructure Area-SourceBuild untriaged
Dominant language
C#
Stars
3.2k
Forks
1.3k
PR merge metrics
PR metrics pending

Description

While building dotnet 9, I have come accross this error that is treated as a warning:

```
2024/11/25 11:47:59 INFO --------------------------------------------------------------------------------------
2024/11/25 11:48:04 INFO 11:48:04 info: BinaryTool[0] Starting binary tool at 11/25/2024 11:48:04 in Clean mode
2024/11/25 11:48:04 INFO 11:48:04 info: BinaryTool[0] Creating directory '/home/build/src/artifacts/log/binary-report' for 'OutputReportDirectory'.
2024/11/25 11:48:04 INFO 11:48:04 info: BinaryTool[0] Detecting binaries in '/home/build/src' not listed in '/home/build/src/eng/allowed-sb-binaries.txt'...
2024/11/25 11:48:09 WARN Unhandled exception: System.ComponentModel.Win32Exception (2): An error occurred trying to start process 'file' with working directory '/home/build/src'
le or directory
2024/11/25 11:48:09 WARN at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo startInfo, String resolvedFilename, String[] argv, String[] envp, String cwd, Boole
tials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
2024/11/25 11:48:09 WARN at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
2024/11/25 11:48:09 WARN at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
2024/11/25 11:48:09 WARN at BinaryToolKit.DetectBinaries.ExecuteProcessAsync(String executable, String arguments) in /home/build/src/eng/tools/BinaryToolKit/DetectBinaries.cs
2024/11/25 11:48:09 WARN at BinaryToolKit.DetectBinaries.IsNotUTF16Async(String file) in /home/build/src/eng/tools/BinaryToolKit/DetectBinaries.cs:line 75
2024/11/25 11:48:09 WARN at BinaryToolKit.DetectBinaries.IsBinaryAsync(String filePath) in /home/build/src/eng/tools/BinaryToolKit/DetectBinaries.cs:line 64
2024/11/25 11:48:09 WARN at BinaryToolKit.DetectBinaries.<>c__DisplayClass3_0.<b__0>d.MoveNext() in /home/build/src/eng/tools/BinaryToolKit/DetectBinaries.cs:li
2024/11/25 11:48:09 WARN --- End of stack trace from previous location ---
2024/11/25 11:48:09 WARN at BinaryToolKit.DetectBinaries.ExecuteAsync(String targetDirectory, String outputReportDirectory, String allowedBinariesFile) in /home/build/src/eng
yToolKit/DetectBinaries.cs:line 34
2024/11/25 11:48:09 WARN at BinaryToolKit.BinaryTool.ExecuteAsync(String targetDirectory, String outputReportDirectory, String allowedBinariesFile, Modes mode) in /home/build
ls/BinaryToolKit/BinaryTool.cs:line 39
2024/11/25 11:48:09 WARN at BinaryToolKit.Program.<>c__DisplayClass7_0.<b__0>d.MoveNext() in /home/build/src/eng/tools/BinaryToolKit/Program.cs:line 79
2024/11/25 11:48:09 WARN --- End of stack trace from previous location ---
2024/11/25 11:48:09 WARN at System.CommandLine.CliCommand.<>c__DisplayClass32_0.<b__0>d.MoveNext()
2024/11/25 11:48:09 WARN --- End of stack trace from previous location ---
2024/11/25 11:48:09 WARN at System.CommandLine.Invocation.InvocationPipeline.InvokeAsync(ParseResult parseResult, CancellationToken cancellationToken)

```

I would like to know if this error that is treated as a warning (as the build process continues and finishes correctly) can have an effect on the produced artifacts.

Thanks.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.