Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release/6.0-staging] Update dependencies from dotnet/arcade #99694

Merge branch 'release/6.0-staging' into darc-release/6.0-staging-8282…

7f85c40
Select commit
Loading
Failed to load commit list.
Merged

[release/6.0-staging] Update dependencies from dotnet/arcade #99694

Merge branch 'release/6.0-staging' into darc-release/6.0-staging-8282…
7f85c40
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime failed Apr 12, 2024 in 3h 29m 22s

Build #20240412.58 had test failures

Details

Tests

  • Failed: 13 (0.00%)
  • Passed: 2,956,912 (98.33%)
  • Other: 50,160 (1.67%)
  • Total: 3,007,085

Annotations

Check failure on line 78 in .packages/microsoft.dotnet.helix.sdk/6.0.0-beta.24204.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.packages/microsoft.dotnet.helix.sdk/6.0.0-beta.24204.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L78

.packages/microsoft.dotnet.helix.sdk/6.0.0-beta.24204.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(78,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item System.IO.Net5Compat.Tests in job 469ad103-ad3e-4122-93d6-68bd020268d9 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/469ad103-ad3e-4122-93d6-68bd020268d9/workitems/System.IO.Net5Compat.Tests/console

Check failure on line 78 in .packages/microsoft.dotnet.helix.sdk/6.0.0-beta.24204.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.packages/microsoft.dotnet.helix.sdk/6.0.0-beta.24204.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L78

.packages/microsoft.dotnet.helix.sdk/6.0.0-beta.24204.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(78,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item System.IO.Net5Compat.Tests in job 8390b772-7072-47d2-92fd-320a94e487d3 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/8390b772-7072-47d2-92fd-320a94e487d3/workitems/System.IO.Net5Compat.Tests/console

Check failure on line 78 in .packages/microsoft.dotnet.helix.sdk/6.0.0-beta.24204.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.packages/microsoft.dotnet.helix.sdk/6.0.0-beta.24204.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L78

.packages/microsoft.dotnet.helix.sdk/6.0.0-beta.24204.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(78,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item System.IO.Tests in job 8390b772-7072-47d2-92fd-320a94e487d3 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/8390b772-7072-47d2-92fd-320a94e487d3/workitems/System.IO.Tests/console

Check failure on line 78 in .packages/microsoft.dotnet.helix.sdk/6.0.0-beta.24204.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.packages/microsoft.dotnet.helix.sdk/6.0.0-beta.24204.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L78

.packages/microsoft.dotnet.helix.sdk/6.0.0-beta.24204.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(78,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item JIT.Generics in job 3d9bf8e0-e236-4166-8e80-313a236fbb22 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/3d9bf8e0-e236-4166-8e80-313a236fbb22/workitems/JIT.Generics/console

Check failure on line 1 in JIT/Generics/Instantiation/Interfaces/class04/class04.sh

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

JIT/Generics/Instantiation/Interfaces/class04/class04.sh

System.IO.IOException: The system cannot open the device or file specified. : 'NuGet-Migrations'
   at System.Threading.Mutex.CreateMutexCore(Boolean initiallyOwned, String name, Boolean& createdNew)
   at System.Threading.Mutex..ctor(Boolean initiallyOwned, String name)
   at NuGet.Common.Migrations.MigrationRunner.Run()
   at Microsoft.DotNet.Configurer.DotnetFirstTimeUseConfigurer.Configure()
   at Microsoft.DotNet.Cli.Program.ConfigureDotNetForFirstTimeUse(IFirstTimeUseNoticeSentinel firstTimeUseNoticeSentinel, IAspNetCertificateSentinel aspNetCertificateSentinel, IFileSentinel toolPathSentinel, Boolean isDotnetBeingInvokedFromNativeInstaller, DotnetFirstRunConfiguration dotnetFirstRunConfiguration, IEnvironmentProvider environmentProvider, Dictionary`2 performanceMeasurements)
   at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, TimeSpan startupTime, ITelemetry telemetryClient)
   at Microsoft.DotNet.Cli.Program.Main(String[] args)

Return code:      1
Raw output file:      /datadisks/disk1/work/AA360911/w/99720878/uploads/Reports/JIT.Generics/Instantiation/Interfaces/class04/class04.output.txt
Raw output:
BEGIN EXECUTION
Test Harness Exitcode is : 1
To run the test:
> set CORE_ROOT=/datadisks/disk1/work/AA360911/p
> /datadisks/disk1/work/AA360911/w/99720878/e/JIT/Generics/Instantiation/Interfaces/class04/class04.sh
Expected: True
Actual:   False
Raw output
   at JIT_Generics._Instantiation_Interfaces_class04_class04_._Instantiation_Interfaces_class04_class04_sh()

Check failure on line 1 in JIT/Methodical/cctor/misc/throw_cs_ro/throw_cs_ro.sh

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

JIT/Methodical/cctor/misc/throw_cs_ro/throw_cs_ro.sh

System.IO.IOException: The system cannot open the device or file specified. : 'NuGet-Migrations'
   at System.Threading.Mutex.CreateMutexCore(Boolean initiallyOwned, String name, Boolean& createdNew)
   at System.Threading.Mutex..ctor(Boolean initiallyOwned, String name)
   at NuGet.Common.Migrations.MigrationRunner.Run()
   at Microsoft.DotNet.Configurer.DotnetFirstTimeUseConfigurer.Configure()
   at Microsoft.DotNet.Cli.Program.ConfigureDotNetForFirstTimeUse(IFirstTimeUseNoticeSentinel firstTimeUseNoticeSentinel, IAspNetCertificateSentinel aspNetCertificateSentinel, IFileSentinel toolPathSentinel, Boolean isDotnetBeingInvokedFromNativeInstaller, DotnetFirstRunConfiguration dotnetFirstRunConfiguration, IEnvironmentProvider environmentProvider, Dictionary`2 performanceMeasurements)
   at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, TimeSpan startupTime, ITelemetry telemetryClient)
   at Microsoft.DotNet.Cli.Program.Main(String[] args)

Return code:      1
Raw output file:      /datadisks/disk1/work/AA360911/w/B2BB099F/uploads/Reports/JIT.Methodical/cctor/misc/throw_cs_ro/throw_cs_ro.output.txt
Raw output:
BEGIN EXECUTION
Test Harness Exitcode is : 1
To run the test:
> set CORE_ROOT=/datadisks/disk1/work/AA360911/p
> /datadisks/disk1/work/AA360911/w/B2BB099F/e/JIT/Methodical/cctor/misc/throw_cs_ro/throw_cs_ro.sh
Expected: True
Actual:   False
Raw output
   at JIT_Methodical._cctor_misc_throw_cs_ro_throw_cs_ro_._cctor_misc_throw_cs_ro_throw_cs_ro_sh()

Check failure on line 1 in JIT.Generics.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

JIT.Generics.WorkItemExecution

The Helix Work Item failed. Often this is due to a test crash or infrastructure failure. See the Helix Test Logs tab in the Results page of Azure DevOps.

Check failure on line 1 in JIT.Methodical.a-dA-D.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

JIT.Methodical.a-dA-D.WorkItemExecution

The Helix Work Item failed. Often this is due to a test crash or infrastructure failure. See the Helix Test Logs tab in the Results page of Azure DevOps.