[release/8.0-staging][browser] Fix WBT timeout (30000ms exceeded) #104947
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
ilonatommy
added
arch-wasm
|
Tagging subscribers to 'arch-wasm': @lewing |
ilonatommy
added
test-enhancement
|
/azp run runtime-wasm |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
Regardless of azure-pipelines response above, it got triggered. |
radekdoulik
approved these changes
Jul 16, 2024
ilonatommy
added
Servicing-approved
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 #104481.
Fixes #104830.
Risk:
Low
This PR changes only the test infrastructure. Instead of trying to launch browser once for 3s, with this PR we try 3 times, 1s each.