Skip to content

browser-wasm linux Release LibraryTests queues timing out #117974

Open

Description

@MihaZupan

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1102465&view=logs&j=4b4629f5-0ceb-510a-c2b0-acfba5e4035a
Build error leg or test failing: Build / browser-wasm linux Release LibraryTests
Pull request: #117946

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": ["Done building Helix work items for scenario WasmTestOn", "The Operation will be canceled. The next steps may not contain expected logs"],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1102465
Error message validated: [Done building Helix work items for scenario WasmTestOn The Operation will be canceled. The next steps may not contain expected logs]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/23/2025 9:52:36 AM UTC

Report

Build Repository Step Name Console log Pull Request
1625907 dotnet/runtime Send to Helix Log #135243

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 1

Activity

  1. added
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    Known Build ErrorUse this to report build issues in the .NET Helix tab
    on Jul 23, 2025
  2. added
    os-browserBrowser variant of arch-wasm
    and removed
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    untriagedNew issue has not been triaged by the area owner
    Known Build ErrorUse this to report build issues in the .NET Helix tab
    on Jul 23, 2025
  3. added
    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
    on Jul 23, 2025
  4. added
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    untriagedNew issue has not been triaged by the area owner
    Known Build ErrorUse this to report build issues in the .NET Helix tab
    on Jul 23, 2025
  5. dotnet-policy-service commented on Jul 23, 2025

    @dotnet-policy-service
    Contributor

    Tagging subscribers to 'arch-wasm': @lewing
    See info in area-owners.md if you want to be subscribed.

  6. removed
    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
    on Jul 23, 2025
  7. added this to the Future milestone on Jul 28, 2025
  8. added
    arch-wasmWebAssembly architecture
    and removed
    arch-wasmWebAssembly architecture
    on Jul 28, 2025
  9. dotnet-policy-service commented on Jul 28, 2025

    @dotnet-policy-service
    Contributor

    Tagging subscribers to 'arch-wasm': @lewing
    See info in area-owners.md if you want to be subscribed.

  10. akoeplinger commented on Jul 31, 2025

    @akoeplinger
    Member

    I checked a couple of the logs and it seems the workitems just finished a tiny bit too late, e.g. 5-30mins after AzDO already hit the timeout. So this looks like classic queue capacity issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Known Build ErrorUse this to report build issues in the .NET Helix tabarch-wasmWebAssembly architecturearea-VM-meta-monoblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'os-browserBrowser variant of arch-wasm

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions