[automated] Merge branch 'release/6.0' => 'release/6.0-staging' #108870
Build Analysis / Build Analysis
failed
Oct 19, 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.
Build Failures
runtime-libraries-coreclr outerloop /
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌Stage Build job libraries_build_windows_x64_Release appears more than once. Job names must be unique within a stage.
-
❌Stage Build job libraries_build_windows_x86_Release appears more than once. Job names must be unique within a stage.
runtime-richnav / Build / Build windows x64 debug / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌.packages\microsoft.sourcelink.common\1.1.0-beta-21480-02\build\Microsoft.SourceLink.Common.targets(53,5): error : Error writing to source link file 'D:\a\_work\1\s\artifacts\obj\runtime.native.System.IO.Ports\netstandard2.0-Debug\runtime.native.System.IO.Ports.sourcelink.json': The process cannot access the file 'D:\a\_work\1\s\artifacts\obj\runtime.native.System.IO.Ports\netstandard2.0-Debug\runtime.native.System.IO.Ports.sourcelink.json' because it is being used by another process.
Known test errors
-
❌System.Formats.Asn1.Tests.Reader.ReadObjectIdentifier.ReadVeryLongOid_WithAppContext - [6.0] Test failure in System.Formats.Asn1 ReadVeryLongOid_WithAppContext: could not load file or assembly in NET48
-
❌System.Formats.Asn1.Tests.Reader.ReadObjectIdentifier.ReadVeryLongOidArc_WithAppContext - [6.0] Test failure in System.Formats.Asn1 ReadVeryLongOid_WithAppContext: could not load file or assembly in NET48
-
❌System.Formats.Asn1.Tests.Reader.ReadObjectIdentifier.ReadVeryLongOid_WithAppContext - [6.0] Test failure in System.Formats.Asn1 ReadVeryLongOid_WithAppContext: could not load file or assembly in NET48
-
❌System.Formats.Asn1.Tests.Reader.ReadObjectIdentifier.ReadVeryLongOidArc_WithAppContext - [6.0] Test failure in System.Formats.Asn1 ReadVeryLongOid_WithAppContext: could not load file or assembly in NET48
-
❌System.IO.Tests.WorkItemExecution - System.IO.Net5Compat.Tests and System.IO.Tests suddenly exiting with error 137
-
❌System.IO.Net5Compat.Tests.WorkItemExecution - System.IO.Net5Compat.Tests and System.IO.Tests suddenly exiting with error 137
-
❌Microsoft.Bcl.AsyncInterfaces.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Configuration.Ini.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Configuration.CommandLine.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Configuration.Xml.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Configuration.FileExtensions.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Configuration.Functional.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.FileProviders.Composite.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.DependencyInjection.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Configuration.Json.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Logging.EventSource.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.DependencyInjection.ExternalContainers.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Configuration.UserSecrets.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.HostFactoryResolver.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Configuration.EnvironmentVariables.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.FileSystemGlobbing.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Configuration.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Primitives.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Hosting.Functional.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Configuration.Binder.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Http.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Caching.Memory.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.FileProviders.Physical.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Logging.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.VisualBasic.Core.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Collections.Concurrent.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Win32.Primitives.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Hosting.Systemd.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Logging.Generators.Roslyn3.11.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Logging.Generators.Roslyn4.0.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Composition.AttributeModel.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.ComponentModel.Annotations.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Collections.Immutable.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.XmlSerializer.Generator.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Logging.Testing.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Options.ConfigurationExtensions.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.ComponentModel.Composition.Registration.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.ComponentModel.TypeConverter.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Composition.TypedParts.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Options.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Collections.NonGeneric.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.ComponentModel.Primitives.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Collections.Specialized.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Composition.Convention.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Composition.Hosting.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.ComponentModel.Composition.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Data.DataSetExtensions.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Diagnostics.DiagnosticSource.Switches.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.ComponentModel.EventBasedAsync.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Composition.Runtime.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Diagnostics.Contracts.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Diagnostics.TextWriterTraceListener.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Diagnostics.StackTrace.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Diagnostics.DiagnosticSource.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌Microsoft.Extensions.Logging.Console.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Diagnostics.Tools.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Diagnostics.TraceSource.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Diagnostics.Tracing.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Globalization.Extensions.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Globalization.Calendars.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Drawing.Primitives.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.IO.FileSystem.DriveInfo.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.IO.Compression.ZipFile.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.IO.MemoryMappedFiles.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.IO.FileSystem.Manual.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Net.Http.Json.Unit.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Net.Mail.Functional.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Net.Http.Enterprise.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Net.Primitives.Functional.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Net.Security.Enterprise.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Net.Primitives.Pal.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌System.Private.Uri.Functional.Tests.WorkItemExecution - WASM tests failing with `Chrome failed to start`
-
❌GC/API/GCHandleCollector/Usage/Usage.sh - [6.0] GC test failures: Handle collector count overflows or underflows
The following build(s) were only partially analyzed due to the number of test errors and helix logs:
- [runtime]
Test Failures (1579 tests failed)
🔹 [All failing tests from runtime]
❌ EMSDK-.InvariantGlobalizationTests.WorkItemExecution [Console] [Details] [Artifacts] [100.00% 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
❌ EMSDK-.MainWithArgsTests.WorkItemExecution [Console] [Details] [Artifacts] [100.00% 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
❌ EMSDK-.NativeBuildTests.WorkItemExecution [Console] [Details] [Artifacts] [100.00% 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
❌ EMSDK-.SatelliteAssembliesTests.WorkItemExecution [Console] [Details] [Artifacts] [100.00% 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
🔹 [All failing tests from runtime-coreclr outerloop]
❌ JIT.WorkItemExecution [Console] [Details] [Artifacts] [6.15% 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]
Loading