You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
So actually there problems was as follows -
The driver was not being stopped, so it kept the test in running state until the BrowserStack 90 seconds Timeout and the BrowserStack Binary was being killed before the drive was being quit. Hence, some of the requests in the test were failing.
Sometimes, in case of sessions running in parallel with same key, it cannot spawn two different binaries with only key parameter, user needs to use local-identifier for each instance of binary.
lockbot
locked as resolved and limited conversation to collaborators
May 5, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
2 participants
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.
So actually there problems was as follows -
The driver was not being stopped, so it kept the test in running state until the BrowserStack 90 seconds Timeout and the BrowserStack Binary was being killed before the drive was being quit. Hence, some of the requests in the test were failing.
Sometimes, in case of sessions running in parallel with same key, it cannot spawn two different binaries with only
key
parameter, user needs to uselocal-identifier
for each instance of binary.