[release/9.0] Update dependencies from dotnet/sdk #108843
Merged
Build Analysis / Build Analysis
succeeded
Oct 17, 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: Failure is https://github.com//issues/108994
- 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.
⚠️ The following pipeline(s) will not be analyzed as has been explicited excluded from analysis
Build Failures
runtime / Build / linux-x64 release Installer_Build_And_Test / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌VSTest(0,0): error : Tests failed: /__w/1/s/artifacts/TestResults/Release/HostActivation.Tests_net9.0_x64.html [net9.0|x64]
runtime / Build / osx-x64 release Installer_Build_And_Test / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌VSTest(0,0): error : Tests failed: /Users/runner/work/1/s/artifacts/TestResults/Release/HostActivation.Tests_net9.0_x64.html [net9.0|x64]
runtime / Build / windows-x64 release Installer_Build_And_Test / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌VSTest(0,0): error : Tests failed: D:\a\_work\1\s\artifacts\TestResults\Release\HostActivation.Tests_net9.0_x64.html [net9.0|x64]
1 other jobs are failing and were not displayed due to space limitations.
Builds with failures: [runtime]
Known test errors
-
❌Microsoft.DotNet.CoreSetup.Test.HostActivation.FrameworkDependentAppLaunch.AppHost_CLI_MissingRuntimeFramework_ErrorReportedInStdErr(missingHostfxr: False) - [release/9.0] HostActivation installer tests are expecting 9.0.0 but getting 9.0.0-ci in PRs
-
❌Wasi.Build.Tests.SdkMissingTests.SimpleBuildDoesNotFail - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.SdkMissingTests.AOTFailsOnlyOnPublish - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.PInvokeTableGeneratorTests.InteropSupportForUnmanagedEntryPointWithoutDelegate - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.WasiTemplateTests.ConsoleBuildAndRunAOT - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.WasiTemplateTests.ConsoleBuildThenRunThenPublish - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.WasiTemplateTests.ConsoleBuildAndRunForDifferentOutputPaths - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.WasiLibraryModeTests.ConsoleBuildLibraryMode - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.HttpTests.HttpBuildThenRunThenPublish - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.InvariantTests.ConsolePublishAndRunForSingleFileBundle_InvariantTimeZone - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.InvariantTests.ConsolePublishAndRunForSingleFileBundle_InvariantGlobalization - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Workloads-ST-Wasm.Build.Tests.WorkItemExecution - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌WasmTestOnChrome-MT-Wasm.Browser.Threads.Sample.WorkItemExecution - [browser][MT] test failure: Tests timed out. Killing driver service
-
❌WasmTestOnChrome-MT-Wasm.Browser.Threads.Sample.WorkItemExecution - [8.0][browser][wasm] Failed trying to read log messages via selenium: OpenQA.Selenium.WebDriverException: An unknown exception was encountered sending an HTTP request to the remote WebDriver server for URL
-
❌Wasi.Build.Tests.InvariantTests.ConsolePublishAndRunForSingleFileBundle_InvariantTimeZone - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.InvariantTests.ConsolePublishAndRunForSingleFileBundle_InvariantGlobalization - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.PInvokeTableGeneratorTests.InteropSupportForUnmanagedEntryPointWithoutDelegate - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.HttpTests.HttpBuildThenRunThenPublish - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.WasiTemplateTests.ConsoleBuildAndRunAOT - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.WasiTemplateTests.ConsoleBuildThenRunThenPublish - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.WasiTemplateTests.ConsoleBuildAndRunForDifferentOutputPaths - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.WasiLibraryModeTests.ConsoleBuildLibraryMode - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.SdkMissingTests.SimpleBuildDoesNotFail - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Wasi.Build.Tests.SdkMissingTests.AOTFailsOnlyOnPublish - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Workloads-ST-Wasm.Build.Tests.WorkItemExecution - [release/9.0][wasi/wasm] SimpleBuildDoesNotFail compares with the wrong expected value
-
❌Microsoft.DotNet.CoreSetup.Test.HostActivation.FrameworkDependentAppLaunch.AppHost_CLI_MissingRuntimeFramework_ErrorReportedInStdErr(missingHostfxr: False) - [release/9.0] HostActivation installer tests are expecting 9.0.0 but getting 9.0.0-ci in PRs
-
❌Wasm.Build.NativeRebuild.Tests.SimpleSourceChangeRebuildTest.SimpleStringChangeInSource - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.EnsureComInteropCompilesInAOT - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.EnsureWasmAbiRulesAreFollowedInAOT - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.DllImportWithFunctionPointers_WarningsAsMessages - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.UCOWithSpecialCharacters - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.UnmanagedStructAndMethodIn_SameAssembly_WithDisableRuntimeMarshallingAttribute_ConsideredBlittable - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.IcallWithOverloadedParametersAndEnum - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.UnmanagedStructsAreConsideredBlittableFromDifferentAssembly - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.UnmanagedStructAndMethodIn_SameAssembly_WithoutDisableRuntimeMarshallingAttribute_NotConsideredBlittable - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.CallIntoLibrariesWithNonAlphanumericCharactersInTheirNames - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.EnsureWasmAbiRulesAreFollowedInInterpreter - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.DllImportWithFunctionPointers_ForVariadicFunction_CompilesWithWarning - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.NativeLibraryWithVariadicFunctions - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.UnmanagedCallback_WithFunctionPointers_CompilesWithWarnings - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.UnmanagedStructAndMethodIn_SameAssembly_WithoutDisableRuntimeMarshallingAttribute_WithStructLayout_ConsideredBlittable - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.DllImportWithFunctionPointersCompilesWithoutWarning - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.BuildNativeInNonEnglishCulture - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.PInvokeTableGeneratorTests.UnmanagedCallback_InFileType - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.Blazor.SimpleRunTests.BlazorBuildRunTest - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.Blazor.SimpleRunTests.BlazorPublishRunTest - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.Blazor.SimpleRunTests.BlazorBuildAndRunForDifferentOutputPaths - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.TestAppScenarios.LazyLoadingTests.FailOnMissingLazyAssembly - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.TestAppScenarios.LazyLoadingTests.LoadLazyAssemblyBeforeItIsNeeded - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
-
❌Wasm.Build.Tests.Blazor.IcuTests.FullIcuFromRuntimePackWithInvariant - [release/9.0][wasi/wasm] Expected the multithreading runtime pack to be available when running on CI (after branch stabilization)
The following build(s) were only partially analyzed due to the number of test errors and helix logs:
- [runtime]
Test Failures (325 tests failed)
🔹 [All failing tests from runtime]
- Exception Message
**WARNING** failure message 'Matching the command error output failed. Pattern: 'details: (?>.|\s)*'Microsoft\.NETCore\.App',\ version\ '9\.0\.0'\ \(x64\)' File Name: D:\a\_work\1\s\artifacts\tests\host\windows.x64.Release\ha\oxwwy3vr.uam\HelloWorld\HelloWorld.exe Arguments: Environment: DOTNET_ROOT = D:\a\_work\1\s\artifacts\tests\host\windows.x64.Release\ha\mc42tgnv.shb\guiMissingFramework DOTNET_ROOT(x86) = D:\a\_work\1\s\artifacts\tests\host\windows.x64.Release\ha\mc42tgnv.shb\guiMissingFramework Exit Code: 0xffffffff StdOut:
StdErr:
Tracing enabled @ Thu Oct 17 21:00:31 2024 GMT
--- Invoked apphost [version: 9.0.0 @Commit: 5466e7f904e8bef31cedbdaaaf14e4d3ae493411] main = {
D:\a\_work\1\s\artifacts\tests\host\windows.x64.Release\ha\oxwwy3vr.uam\HelloWorld\HelloWorld.exe
}
Redirecting errors to custom writer.
The managed DLL bound to this executable is: 'HelloWorld.dll'
.NET root search location options: 0
Using environment variable DOTNET_ROOT=[D:\a\_work\1\s [Full log]- CallStack
at FluentAssertions.Execution.XUnit2TestFramework.Throw(String message) at FluentAssertions.Execution.TestFrameworkProvider.Throw(String message) at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message) at FluentAssertions.Execution.AssertionScope.FailWith(Func`1 failReasonFunc) at Microsoft.DotNet.CoreSetup.Test.CommandResultAssertions.HaveStdErrMatching(String pattern, RegexOptions options) in /_/src/installer/tests/TestUtils/Assertions/CommandResultAssertions.cs:line 112 at Microsoft.DotNet.CoreSetup.Test.HostActivation.FrameworkDependentAppLaunch.AppHost_GUI_MissingRuntimeFramework_ErrorReportedInDialog() in /_/src/installer/tests/HostActivation.Tests/FrameworkDependentAppLaunch.cs:line 352 at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor) at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)... [Full call stack]
❌ Microsoft.DotNet.CoreSetup.Test.HostActivation.FrameworkDependentAppLaunch.AppHost_GUI_MissingRuntimeFramework_ErrorReportedInDialog [Details] [2.33% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configurations (2)
❌ NoWorkload-NoWebcil-ST-Wasm.Build.Tests.WorkItemExecution [Console] [Details] [Artifacts] [4.57% 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)
❌ NoWorkload-ST-Wasm.Build.Tests.WorkItemExecution [Console] [Details] [Artifacts] [3.40% 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)
❌ System.Net.HttpListener.Tests.WorkItemExecution [Console] [Details] [Artifacts] [1.05% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: Timeout. To investigate look the [Console log] / navigate to [Helix Artifacts]
Failing Configuration
Was this helpful?
Loading