[wasm][debugger] Disable failing multithreading debugger tests #86501
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Tagging subscribers to this area: @thaystg Issue DetailsConnected issue: #86496
|
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
radical
reviewed
May 19, 2023
|
@ilonatommy but the multithreaded lane is still failing in this PR, right? |
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ilonatommy
requested review from
lewing,
pavelsavara,
kg and
marek-safar
as code owners
radical
reviewed
May 22, 2023
src/libraries/Common/tests/TestUtilities/System/PlatformDetection.cs
Outdated
Show resolved
Hide resolved
|
/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. |
kg
approved these changes
Jun 5, 2023
|
/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 |
radical
changed the title
radical
approved these changes
Jun 5, 2023
|
/azp run runtime-wasm-dbgtests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
radical
approved these changes
Jun 6, 2023
|
Failure is unrelated. |
radical
added a commit
to radical/runtime
that referenced
this pull request
Jun 7, 2023
.. by making sure to escape `&` in the command line. This was introduced in: ``` commit e96321d Author: Ilona Tomkowicz <32700855+ilonatommy@users.noreply.github.com> 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.
radical
added a commit
that referenced
this pull request
Jun 8, 2023
* [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 <32700855+ilonatommy@users.noreply.github.com> 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
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.