Add support for building with Clang 19 #109198
Merged
Build Analysis / Build Analysis
succeeded
Nov 26, 2024 in 0s
.NET Result Analysis
Details
‼️ Build Analysis Check Result has been manually overridden
- The build analysis check result has been updated by the user for the following reason: Failures are unrelated
- The check result has changed from Failure to Success
Tip
To unconditionally bypass the build analysis check (turn it green), you can use the escape mechanism feature. The completion time may vary, potentially taking several minutes, depending on the build analysis workload at the moment.
Build Failures
dotnet-linker-tests / Build / windows-x64 release Runtime_Release / Run Trimming Tests
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌eng\testing\linker\trimmingTests.targets(155,5): error : Error: [Failed Test]: D:\a\_work\1\s\src\libraries\System.Net.Http\tests\TrimmingTests\HttpClientTest.cs. The Command D:\a\_work\1\s\artifacts\bin\trimmingTests\projects\System.Net.Http.TrimmingTests\HttpClientTest\win-x64\bin\Release\net8.0\win-x64\publish\project return a non-success exit code.
Known test errors
-
❌Wasm.Build.NativeRebuild.Tests.OptimizationFlagChangeTests.OptimizationFlagChange - [8.0][browser][wasm] emcc failure to compile aot-instances
-
❌Workloads-Wasm.Build.NativeRebuild.Tests.OptimizationFlagChangeTests.WorkItemExecution - [8.0][browser][wasm] emcc failure to compile aot-instances
Test Failures (1 tests failed)
🔹 [All failing tests from runtime]
❌ System.Text.Json.Tests.WorkItemExecution [Console] [Details] [Artifacts] [6.81% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: BadExit. To investigate look the [Console log] / navigate to [Helix Artifacts]
Failing Configuration
Was this helpful?
Loading