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

[wasm] Defer parsing of wasm stack symbolication maps #99974

Merged
merged 3 commits into from
Mar 21, 2024

Only allow one symbol map file

83bc8af
Select commit
Loading
Failed to load commit list.
Merged

[wasm] Defer parsing of wasm stack symbolication maps #99974

Only allow one symbol map file
83bc8af
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime failed Mar 21, 2024 in 1h 55m 27s

Build #20240320.58 had test failures

Details

Tests

  • Failed: 1 (0.00%)
  • Passed: 450,686 (96.88%)
  • Other: 14,490 (3.11%)
  • Total: 465,177

Annotations

Check failure on line 91 in .packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24165.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.24165.6/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L91

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24165.6/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item WasmTestOnBrowser-System.Runtime.InteropServices.JavaScript.Tests in job d5b227df-6c14-4e7e-b741-d82f3af8d319 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/d5b227df-6c14-4e7e-b741-d82f3af8d319/workitems/WasmTestOnBrowser-System.Runtime.InteropServices.JavaScript.Tests/console

Check failure on line 1 in WasmTestOnBrowser-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

WasmTestOnBrowser-System.Runtime.InteropServices.JavaScript.Tests.WorkItemExecution

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