[release/7.0-staging] [wasm][debugger] Set VSTEST_TESTHOST_SHUTDOWN_TIMEOUT to 2s #89862
Conversation
This file contains hidden or 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
The tests have been getting randomly aborted with: `The active test run was aborted. Reason: Test host process crashed` This might be due to the shutdown taking too long. The default timeout is 100ms. Increasing that to 2000ms. Issue: #89409
ghost
added
the
needs-area-label
radical
approved these changes
Aug 2, 2023
Member
|
This is a tests only change. |
thaystg
added
Servicing-approved
This was referenced Aug 2, 2023
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.
Backport of #89703 to release/7.0-staging
/cc @thaystg @radical
Customer Impact
None. Only trying to get CI green.
Testing
Risk
None.
IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging, notrelease/X.0.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.