Do not wait for reporter is executed when concurrency is enabled (closes #4894) #4942
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
|
❌ Tests for the commit dc8daa7 have failed. See details: |
|
@testcafe-build-bot retest |
|
✅ Tests for the commit dc8daa7 have passed. See details: |
AlexKamaev
changed the title
|
I created the #4951 issue about concurrency |
AndreyBelym
approved these changes
Apr 7, 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.
If we have multiple fixtures and every fixture contains small number of tests, the synchronization occurs too often. This leads to the situation when concurrent browsers wait for last test in fixture is done.
I remove the syncronization when the concurrency mode is enabled