Details
-
Improvement
-
Status: Resolved
-
P2
-
Resolution: Fixed
-
None
-
None
Description
Usage of forkEvery 1 is typically a strong sign of poor quality / bad code and should be avoided:
- It significantly impacts performance when running tests.
- And it often hides resource leaks, either in code or worse in the runner itself.
Attachments
Issue Links
- fixes
-
BEAM-11653 MetricsSinkTest is failing with Spark 3
- Resolved
- links to