[wasm][debugger] Disable failing multithreading debugger tests#86501
[wasm][debugger] Disable failing multithreading debugger tests#86501radical merged 16 commits intodotnet:mainfrom
Conversation
|
Tagging subscribers to this area: @thaystg Issue DetailsConnected issue: #86496
|
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@ilonatommy but the multithreaded lane is still failing in this PR, right? |
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
I cannot reproduce any DebuggerTests_MultiThreaded on Windows. Linux's most frequent failures are blocked. |
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This reverts commit 2e008d4.
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Use |
|
/azp run runtime-wasm-dbgtests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Failure is unrelated. |
.. by making sure to escape `&` in the command line. This was introduced in: ``` commit e96321d Author: Ilona Tomkowicz <[email protected]> Date: Tue Jun 6 05:59:43 2023 +0200 [wasm][debugger] Disable failing multithreading debugger tests (dotnet#86501) ``` .. but missed CI due to the helix outage.
* [wasm] Fix running debugger tests on windows .. by making sure to escape `&` in the command line. This was introduced in: ``` commit e96321d Author: Ilona Tomkowicz <[email protected]> Date: Tue Jun 6 05:59:43 2023 +0200 [wasm][debugger] Disable failing multithreading debugger tests (#86501) ``` .. but missed CI due to the helix outage. * Fix escaping ! on windows
Connected issue: #86496
CI is triggered by MsBuild and we had no failing category filter there. Category in
dotnet testfilter is case sensitive, should be lowercased.To clean the timeout issues with single threaded debugging tests, this PR increases the timeout to 15 minutes (3 x the original value).Increasing the timeout has no effect.