Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-14334

Avoid using forkEvery in Spark runner tests

Details

    • Improvement
    • Status: Resolved
    • P2
    • Resolution: Fixed
    • None
    • 2.40.0
    • runner-spark, testing
    • 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

          Activity

            People

              mosche Moritz Mack
              mosche Moritz Mack
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 12h
                  12h