goutamadwant opened a new pull request, #12013:
URL: https://github.com/apache/seatunnel/pull/12013

   ### Purpose of this pull request
   
   Fixes #12012.
   
   
`CoordinatorServiceTest.testClearCoordinatorServiceDropsPendingJobsUnderRejectStrategy`
 waited for the pending-job scheduler by polling Mockito while 
`preApplyResources()` was still running on another thread. On a loaded Java 8 
CI runner, that polling condition timed out even though the test was only 
trying to establish that the scheduler had entered the mocked method.
   
   This PR replaces the polling synchronization with a `CountDownLatch` 
signalled from inside `preApplyResources()`. The test now waits for the exact 
scheduler-entry event with a bounded timeout before clearing the coordinator.
   
   Only test code changes. Coordinator scheduling and cleanup behavior are 
unchanged.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   - Ran the focused regression test five consecutive times on Java 8: 5 passed.
   - Ran the complete `CoordinatorServiceTest` on Java 8: 35 tests, 0 failures, 
0 errors, 2 skipped.
   - Ran the complete `CoordinatorServiceTest` on Java 11: 35 tests, 0 
failures, 0 errors, 2 skipped.
   - Ran the Java 8 reactor install for `seatunnel-engine-server` and its 
dependencies with tests skipped: 40 modules passed.
   - Spotless and `git diff --check` passed.
   
   ### Check list
   
   * [x] No new Jar binary package is added.
   * [x] Documentation is not required because this is a test-only 
stabilization.
   * [x] `incompatible-changes.md` is not required because runtime behavior is 
unchanged.
   * [x] Connector checklist is not applicable because no connector code is 
changed.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to