[wasm][release/9.0] Test SteppingIntoLibrarySymbolsLoadedFromSymbolServerAddOtherSymbolServerAndStepAgain timeouts

Open
#116,368 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
wasm
Domain
devtools, testing

Research direction

Start with the chrome-DebuggerTests.WorkItemExecution failure in build 1058553 and the test named SteppingIntoLibrarySymbolsLoadedFromSymbolServerAddOtherSymbolServerAndStepAgain. Review the linked pull request and available build logs to identify the timeout context. Done means the test completes successfully without timing out in the affected WASM debugger run.

Written by the indexing model from the issue text.

Description

arch-wasm area-Debugger-mono Known Build Error

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1058553
Build error leg or test failing: chrome-DebuggerTests.SteppingTests.WorkItemExecution
Pull request: https://github.com/dotnet/runtime/pull/114682

Error Message

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

{
  "ErrorMessage": "DebuggerTests.SteppingTests.SteppingIntoLibrarySymbolsLoadedFromSymbolServerAddOtherSymbolServerAndStepAgain [FAIL]",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}
Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1058553
Error message validated: [DebuggerTests.SteppingTests.SteppingIntoLibrarySymbolsLoadedFromSymbolServerAddOtherSymbolServerAndStepAgain [FAIL]]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 6/6/2025 10:20:00 AM UTC

Report
Summary
24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
Dominant language
C#
Stars
18.3k
Forks
5.6k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.