Disable some flaky scalatest's tests #12937
Merged
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
We usually don't notice these failures because the community build retries a project up to three times in case of failure, but sometimes all three of them fail, and even when it succeeds it means that community_build_a sometimes takes much longer than it needs to (2 hours instead of 1 hour). I'v reported this upstream at scalatest/scalatest#2049.
anatoliykmetyuk
approved these changes
Jun 29, 2021
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.
We usually don't notice these failures because the community build
retries a project up to three times in case of failure, but sometimes
all three of them fail, and even when it succeeds it means that
community_build_a sometimes takes much longer than it needs to (2 hours
instead of 1 hour).
I'v reported this upstream at
scalatest/scalatest#2049.