Skip to content

[wasm][debugger] Multiple tests failing on rolling builds on Windows #81792

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.

Sign up for GitHub

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

Jump to bottom
Closed
radical opened this issue Feb 7, 2023 · 4 comments
Closed

[wasm][debugger] Multiple tests failing on rolling builds on Windows #81792

radical opened this issue Feb 7, 2023 · 4 comments
Assignees
@radical @thaystg
Labels
arch-wasm WebAssembly architecture area-Debugger-mono Known Build Error Use this to report build issues in the .NET Helix tab test-failure
Milestone
8.0.0

Comments

@radical
Copy link
Member

radical commented Feb 7, 2023 •
edited by build-analysis bot
Loading

Multiple tests are failing on rolling build. One of them(log):

DebuggerTests.ArrayTests.InspectValueTypeArrayLocalsInAsyncInstanceStructMethod(use_cfo: False) [FAIL]
  Failed DebuggerTests.ArrayTests.InspectValueTypeArrayLocalsInAsyncInstanceStructMethod(use_cfo: False) [1 ms]
  Error Message:
   System.Threading.Tasks.TaskCanceledException : Command Profiler.enable timed out during init for the test.Remaining commands: [Debugger.enable: Canceled], [Runtime.runIfWaitingForDebugger: Canceled], [Debugger.setAsyncCallStackDepth: Canceled], [Target.setAutoAttach: Canceled], [app-ready: Canceled].Total time: 60.0025634
  Stack Trace:
     at DebuggerTests.Inspector.OpenSessionAsync(Func`3 getInitCmds, TimeSpan span) in /_/src/mono/wasm/debugger/DebuggerTestSuite/Inspector.cs:line 380
   at DebuggerTests.DebuggerTestBase.InitializeAsync() in /_/src/mono/wasm/debugger/DebuggerTestSuite/DebuggerTestBase.cs:line 167
  Standard Output Messages:
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Information: [testId: 12] New test request for test id 12
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [12] Starting C:\helix\work\correlation\chrome-win\chrome.exe with --headless --disable-gpu --lang=en-US --incognito --remote-debugging-port=0 http://localhost:9400/debugger-driver.html
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr [0207/205924.805:ERROR:registration_protocol_win.cc(135)] TransactNamedPipe: The pipe has been ended. (0x6D)
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr [0207/205924.856:ERROR:network_change_notifier_win.cc(222)] WSALookupServiceBegin failed with: 0
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr 
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr DevTools listening on ws://127.0.0.1:49281/devtools/browser/11cc8e69-f3f3-4632-8b76-52610f837d6d
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr [0207/205924.947:ERROR:dxva_video_decode_accelerator_win.cc(1453)] DXVAVDA fatal error: could not LoadLibrary: mf.dll: The specified module could not be found. (0x7E)
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr [0207/205924.954:ERROR:dxva_video_decode_accelerator_win.cc(1453)] DXVAVDA fatal error: could not LoadLibrary: mfplat.dll: The specified module could not be found. (0x7E)
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr [0207/205924.956:ERROR:dxva_video_decode_accelerator_win.cc(1453)] DXVAVDA fatal error: could not LoadLibrary: msmpeg2vdec.dll: The specified module could not be found. (0x7E)
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr [0207/205924.959:ERROR:dxva_video_decode_accelerator_win.cc(1457)] DXVAVDA fatal error: could not LoadLibrary: dxva2.dll: The specified module could not be found. (0x7E)
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr [0207/205924.961:ERROR:dxva_video_decode_accelerator_win.cc(1461)] DXVAVDA fatal error: could not LoadLibrary: msvproc.dll: The specified module could not be found. (0x7E)
 | [2023-02-07T20:59:25] DebuggerTests.TestHarnessProxy Information: [testId: 12] launching proxy for ws://127.0.0.1:49281/devtools/page/993BC43AA975F885A273B5A0EF15F96A
 | [2023-02-07T20:59:25] Inspector-12 Information: waiting for the runtime to be ready
 | [2023-02-07T20:59:25] DebuggerTests.TestHarnessProxy Debug: [testId: 11] TestHarnessStartup done
 | [2023-02-07T20:59:25] DebuggerTests.TestHarnessProxy Debug: TestHarnessStartup: closing for 11

{
   "BuildRetry": false,
   "ErrorPattern": ".*System.Threading.Tasks.TaskCanceledException : Command Profiler.enable timed out during init for the test.Remaining commands:.*"
}

Report

Build Definition Test Pull Request
163095 dotnet/runtime chrome-DebuggerTests.SteppingTests.WorkItemExecution #81541
163733 dotnet/runtime chrome-DebuggerTests.SteppingTests.WorkItemExecution #81811
163251 dotnet/runtime chrome-DebuggerTests.SteppingTests.WorkItemExecution #81518
163596 dotnet/runtime chrome-DebuggerTests.SetVariableValueTests.WorkItemExecution #79169
163564 dotnet/runtime chrome-DebuggerTests.MonoJsTests.WorkItemExecution #81806
163555 dotnet/runtime chrome-DebuggerTests.MonoJsTests.WorkItemExecution #81611
163423 dotnet/runtime chrome-DebuggerTests.SetVariableValueTests.WorkItemExecution #74623
163245 dotnet/runtime chrome-DebuggerTests.PointerTests.WorkItemExecution #81732
163174 dotnet/runtime chrome-DebuggerTests.GetPropertiesTests.WorkItemExecution #79169
163068 dotnet/runtime DebuggerTests.EvaluateOnCallFrameTests.DebuggerTests.EvaluateOnCallFrameTests.EvaluateTypeInstanceMembers #79127
163000 dotnet/runtime chrome-DebuggerTests.SteppingTests.WorkItemExecution #79339
163015 dotnet/runtime chrome-DebuggerTests.SetVariableValueTests.WorkItemExecution
163001 dotnet/runtime chrome-DebuggerTests.SetVariableValueTests.WorkItemExecution #79339

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
@radical radical added arch-wasm WebAssembly architecture blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' area-Debugger-mono test-failure labels Feb 7, 2023
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Feb 7, 2023
@ghost
Copy link

ghost commented Feb 7, 2023

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

Issue Details

Multiple tests are failing on rolling build. One of them(log):

DebuggerTests.ArrayTests.InspectValueTypeArrayLocalsInAsyncInstanceStructMethod(use_cfo: False) [FAIL]
  Failed DebuggerTests.ArrayTests.InspectValueTypeArrayLocalsInAsyncInstanceStructMethod(use_cfo: False) [1 ms]
  Error Message:
   System.Threading.Tasks.TaskCanceledException : Command Profiler.enable timed out during init for the test.Remaining commands: [Debugger.enable: Canceled], [Runtime.runIfWaitingForDebugger: Canceled], [Debugger.setAsyncCallStackDepth: Canceled], [Target.setAutoAttach: Canceled], [app-ready: Canceled].Total time: 60.0025634
  Stack Trace:
     at DebuggerTests.Inspector.OpenSessionAsync(Func`3 getInitCmds, TimeSpan span) in /_/src/mono/wasm/debugger/DebuggerTestSuite/Inspector.cs:line 380
   at DebuggerTests.DebuggerTestBase.InitializeAsync() in /_/src/mono/wasm/debugger/DebuggerTestSuite/DebuggerTestBase.cs:line 167
  Standard Output Messages:
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Information: [testId: 12] New test request for test id 12
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [12] Starting C:\helix\work\correlation\chrome-win\chrome.exe with --headless --disable-gpu --lang=en-US --incognito --remote-debugging-port=0 http://localhost:9400/debugger-driver.html
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr [0207/205924.805:ERROR:registration_protocol_win.cc(135)] TransactNamedPipe: The pipe has been ended. (0x6D)
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr [0207/205924.856:ERROR:network_change_notifier_win.cc(222)] WSALookupServiceBegin failed with: 0
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr 
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr DevTools listening on ws://127.0.0.1:49281/devtools/browser/11cc8e69-f3f3-4632-8b76-52610f837d6d
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr [0207/205924.947:ERROR:dxva_video_decode_accelerator_win.cc(1453)] DXVAVDA fatal error: could not LoadLibrary: mf.dll: The specified module could not be found. (0x7E)
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr [0207/205924.954:ERROR:dxva_video_decode_accelerator_win.cc(1453)] DXVAVDA fatal error: could not LoadLibrary: mfplat.dll: The specified module could not be found. (0x7E)
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr [0207/205924.956:ERROR:dxva_video_decode_accelerator_win.cc(1453)] DXVAVDA fatal error: could not LoadLibrary: msmpeg2vdec.dll: The specified module could not be found. (0x7E)
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr [0207/205924.959:ERROR:dxva_video_decode_accelerator_win.cc(1457)] DXVAVDA fatal error: could not LoadLibrary: dxva2.dll: The specified module could not be found. (0x7E)
 | [2023-02-07T20:59:24] DebuggerTests.TestHarnessProxy Debug: [testId: 12] browser-stderr [0207/205924.961:ERROR:dxva_video_decode_accelerator_win.cc(1461)] DXVAVDA fatal error: could not LoadLibrary: msvproc.dll: The specified module could not be found. (0x7E)
 | [2023-02-07T20:59:25] DebuggerTests.TestHarnessProxy Information: [testId: 12] launching proxy for ws://127.0.0.1:49281/devtools/page/993BC43AA975F885A273B5A0EF15F96A
 | [2023-02-07T20:59:25] Inspector-12 Information: waiting for the runtime to be ready
 | [2023-02-07T20:59:25] DebuggerTests.TestHarnessProxy Debug: [testId: 11] TestHarnessStartup done
 | [2023-02-07T20:59:25] DebuggerTests.TestHarnessProxy Debug: TestHarnessStartup: closing for 11
Author: radical
Assignees: -
Labels:

arch-wasm, blocking-clean-ci, area-Debugger-mono, test-failure
Milestone: -

@runfoapp runfoapp bot mentioned this issue Feb 7, 2023
Closed
@radical radical added the Known Build Error Use this to report build issues in the .NET Helix tab label Feb 7, 2023
@radical radical added this to the 8.0.0 milestone Feb 7, 2023
@ghost ghost removed the untriaged New issue has not been triaged by the area owner label Feb 7, 2023
@radical
Copy link
Member Author

radical commented Feb 8, 2023

This seems to be related to chrome version. It was working fine with 109.0.5414.119, but fails with the latest stable 110.0.5481.77.

It is reproducible on codespaces, for example when running tests for AssignmentTests .

radical added a commit to radical/runtime that referenced this issue Feb 8, 2023
@radical
[wasm] Pin the version of chrome used for tests
c8ac026 
Related: dotnet#81792

The debugger tests are breaking with the latest stable chrome version
`110.0.5481.77`. As a temporary workaround to keep the CI green, pin the
version to the previous working one.
@radical radical mentioned this issue Feb 8, 2023
Merged
radical added a commit that referenced this issue Feb 8, 2023
@radical
[wasm] Pin the version of chrome used for tests - 109.0.5414.119 (#…
b874537 
…81814)

* [wasm] Pin the version of chrome used for tests

Related: #81792

The debugger tests are breaking with the latest stable chrome version
`110.0.5481.77`. As a temporary workaround to keep the CI green, pin the
version to the previous working one.

* fix windows url
@radical radical added Known Build Error Use this to report build issues in the .NET Helix tab and removed blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab labels Feb 8, 2023
@fanyang-mono fanyang-mono mentioned this issue Feb 8, 2023
Merged
@ManickaP ManickaP mentioned this issue Feb 10, 2023
Merged
radical added a commit to radical/runtime that referenced this issue Mar 8, 2023
@radical
[wasm] Revert to using latest chrome for testing
a6443a5 
dotnet#81792
@radical radical mentioned this issue Mar 8, 2023
Merged
radical added a commit that referenced this issue Mar 8, 2023
@radical
[wasm] Revert to using latest chrome for testing (#83150)
f5fd94b 
#81792
@radical
Copy link
Member Author

radical commented Mar 8, 2023

@thaystg Should this be closed? On CI it seems to pass with the latest stable (111.x). Is it true on codespaces too?

@thaystg
Copy link
Member

thaystg commented Mar 8, 2023

Yeah, I've just tested on codespaces and it's working, let me close.

@thaystg thaystg closed this as completed Mar 8, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Apr 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@radical radical

@thaystg thaystg

Labels
arch-wasm WebAssembly architecture area-Debugger-mono Known Build Error Use this to report build issues in the .NET Helix tab test-failure
Projects
None yet
Milestone
8.0.0
Development

No branches or pull requests
2 participants
@radical @thaystg