Add match_timeout at firefox launch second time to avoid needles mismatch #10369
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
jouyingbin
changed the title
jouyingbin
force-pushed
the
firefox_nss_timeout
branch
from
7e0d6a5
to
c5a3593
Compare
1. Add match_timeout => 360 at firefox launch second time 2. Avoid the mismatch while worker is too busy to response
jouyingbin
force-pushed
the
firefox_nss_timeout
branch
from
c5a3593
to
28797f1
Compare
lilyeyes
approved these changes
May 26, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The issue only can be reproduced on s390x ENV mode, and it could be the worker is too busy to respond, more likely the s390x performance problem, so it can be reproduced while job is too busy.