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/9.0] [mono] Fix crash in emit_llvmonly_handler_start #107590

Merged
merged 4 commits into from
Sep 16, 2024

Merge branch 'release/9.0' into backport/pr-107461-to-release/9.0

18b1ac8
Select commit
Loading
Failed to load commit list.
Merged

[release/9.0] [mono] Fix crash in emit_llvmonly_handler_start #107590

Merge branch 'release/9.0' into backport/pr-107461-to-release/9.0
18b1ac8
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime failed Sep 17, 2024 in 2h 40m 38s

Build #20240916.87 had test failures

Details

Tests

  • Failed: 1 (0.00%)
  • Passed: 1,762,034 (97.71%)
  • Other: 41,309 (2.29%)
  • Total: 1,803,344

Annotations

Check failure on line 91 in .packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24459.6/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24459.6/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L91

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24459.6/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item WasmTestOnChrome-MT-System.IO.FileSystem.Tests in job bd11cd64-ba15-41a9-8e09-f178d7f95f3b has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/bd11cd64-ba15-41a9-8e09-f178d7f95f3b/workitems/WasmTestOnChrome-MT-System.IO.FileSystem.Tests/console

Check failure on line 1 in WasmTestOnChrome-MT-System.IO.FileSystem.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

WasmTestOnChrome-MT-System.IO.FileSystem.Tests.WorkItemExecution

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.