Fix BufferExtensions.Write to specify sizeHint to GetSpan #110047
Closed
Build Analysis / Build Analysis
failed
Nov 21, 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 Infrastructure Errors
Build Failures
runtime / Build / browser-wasm linux Release LibraryTests
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌The job running on agent NetCore-Public 169 ran longer than the maximum time of 240 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
Known test errors
Test Failures (48 tests failed)
🔹 [All failing tests from runtime]
- Centos.8.Amd64.Open
- Debian.11.Amd64.Open
- net10.0-linux-Debug-x64-Mono_Interpreter_Debug-Ubuntu.2204.Amd64.Open
- Centos.8.Amd64.Open
- Debian.11.Amd64.Open
- net10.0-linux-Debug-x64-Mono_Minijit_Debug-Ubuntu.2204.Amd64.Open
- Ubuntu.2204.Arm64.Open
- Debian.11.Arm64.Open
- net10.0-osx-Debug-x64-Mono_Minijit_Debug-OSX.1200.Amd64.Open
- Alpine.317.Amd64.Open
- Ubuntu.2204.Amd64
- Centos.8.Amd64.Open
- Debian.11.Amd64.Open
- net10.0-linux-Debug-x64-coreclr_release-Ubuntu.2204.Amd64.Open
- net10.0-osx-Debug-x64-coreclr_checked-OSX.1200.Amd64.Open
- net10.0-osx-Debug-x64-coreclr_release-OSX.1200.Amd64.Open
- Windows.Amd64.Server2022.Open
- net10.0-windows-Release-x86-coreclr_release-Windows.Amd64.Server2022.Open
- net10.0-windows-Debug-x64-coreclr_release-Windows.81.Amd64.Open
- net10.0-windows-Debug-x64-coreclr_release-Windows.Amd64.Server2022.Open
- net10.0-windows-Debug-x64-coreclr_release-Windows.11.Amd64.Client.Open
- Windows.Nano.1809.Amd64.Open
- Exception Message
Assert.Equal() Failure: Values differ Expected: 12 Actual: 2
- CallStack
at System.Buffers.Tests.BuffersExtensionsTests.WritingToMultiSegmentBuffer() in /_/src/libraries/System.Memory/tests/BuffersExtensions/BuffersExtensionsTests.cs:line 27 at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) in /_/src/mono/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.Mono.cs:line 22 at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs:line 57
- Centos.8.Amd64.Open
- Debian.11.Amd64.Open
- net10.0-linux-Debug-x64-Mono_Interpreter_Debug-Ubuntu.2204.Amd64.Open
- Centos.8.Amd64.Open
- Debian.11.Amd64.Open
- net10.0-linux-Debug-x64-Mono_Minijit_Debug-Ubuntu.2204.Amd64.Open
- Ubuntu.2204.Arm64.Open
- Debian.11.Arm64.Open
- net10.0-osx-Debug-x64-Mono_Minijit_Debug-OSX.1200.Amd64.Open
- Alpine.317.Amd64.Open
- Ubuntu.2204.Amd64
- Centos.8.Amd64.Open
- Debian.11.Amd64.Open
- net10.0-linux-Debug-x64-coreclr_release-Ubuntu.2204.Amd64.Open
- net10.0-osx-Debug-x64-coreclr_checked-OSX.1200.Amd64.Open
- net10.0-osx-Debug-x64-coreclr_release-OSX.1200.Amd64.Open
- Windows.Amd64.Server2022.Open
- net10.0-windows-Release-x86-coreclr_release-Windows.Amd64.Server2022.Open
- net10.0-windows-Debug-x64-coreclr_release-Windows.81.Amd64.Open
- net10.0-windows-Debug-x64-coreclr_release-Windows.Amd64.Server2022.Open
- net10.0-windows-Debug-x64-coreclr_release-Windows.11.Amd64.Client.Open
- Windows.Nano.1809.Amd64.Open
- Exception Message
Assert.False() Failure Expected: False Actual: True
- CallStack
at System.IO.Pipelines.Tests.PipelineReaderWriterFacts.HelloWorldAcrossTwoBlocks() in /_/src/libraries/System.IO.Pipelines/tests/PipeReaderWriterFacts.cs:line 183 --- End of stack trace from previous location ---
❌ System.Buffers.Tests.BuffersExtensionsTests.WritingToMultiSegmentBuffer [Console] [Details] [Artifacts] [0.01% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configurations (22)
❌ System.IO.Pipelines.Tests.PipelineReaderWriterFacts.HelloWorldAcrossTwoBlocks [Console] [Details] [Artifacts] [0.01% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configurations (22)
❌ WasmTestOnChrome-ST-System.IO.Pipelines.Tests.WorkItemExecution [Console] [Details] [Artifacts] [0.11% 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 Configurations (2)
❌ WasmTestOnChrome-ST-System.Memory.Tests.WorkItemExecution [Console] [Details] [Artifacts] [13.72% 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 Configurations (2)
Was this helpful?
Loading