Use correct IL offset when reporting dataflow warnings for return statements #105661
Build Analysis / Build Analysis
succeeded
Aug 7, 2024 in 0s
.NET Result Analysis
Details
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.
⚠️ The following pipeline(s) will not be analyzed as has been explicited excluded from analysis
Known test errors
-
❌System.Tests.StringSplitTests.SplitCharSeparator - [wasm][aot] StringSplitTests and ArrayTests failing with NullReferenceException
-
❌System.Tests.ArrayTests.Sort_Array_Array_Generic - [wasm][aot] StringSplitTests and ArrayTests failing with NullReferenceException
-
❌WasmTestOnV8-ST-System.Runtime.Tests.WorkItemExecution - [wasm][aot] StringSplitTests and ArrayTests failing with NullReferenceException
-
❌Wasm.Build.Tests.Blazor.WorkloadRequiredTests.WorkloadNotRequiredForInvariantGlobalization - [wasm] WBT: Blazor tests on windows failing with `Failed to bind to address` for random ports
-
❌NoWorkload-NoWebcil-ST-Wasm.Build.Tests.WorkItemExecution - [wasm] WBT: Blazor tests on windows failing with `Failed to bind to address` for random ports
-
❌WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution - [browser][MT] WasmBrowserTestRunner.RunConsoleMessagesPump - abrupt disconect
-
❌WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution - [mt][browser] `HttpClient_CancelInDifferentThread` failing with operation cancelled
-
❌WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution - Wasm test failure: Tests timed out. Killing driver service
-
❌WasmTestOnFirefox-MT-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution - [browser][MT] System.Runtime.InteropServices.JavaScript.Tests CI timeouts
Was this helpful?
Loading