[SPARK-37663][CORE][TESTS] Mitigate ConcurrentModificationException thrown from tests in SparkContextSuite #34922
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.
What changes were proposed in this pull request?
This PR fixes an issue that some tests in
SparkContextSuite
can throwConcurrentModificationException
with Scala 2.13.https://github.com/apache/spark/runs/4543047740?check_suite_focus=true#step:9:20851
The cause seems to be same as SPARK-37315 (#34583).
You can easily reproduce this issue by applying the following diff to
master
.Why are the changes needed?
Fix the flaky test.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Locally checked that no
ConcurrentModificationException
is thrown even if a sleep is inserted like the diff shown above.