zhangshenghang opened a new pull request, #12381: URL: https://github.com/apache/seatunnel/pull/12381
### Purpose of this PR Two unit tests keep failing on loaded CI runners even though the behavior under test is correct. Both failures trace to timing budgets that are tighter than the scheduling stalls those runners exhibit. Test-only change; no production code is touched. **1. `PayPalClientTest.closeWakesRetryWait` (Windows)** Failed again on apache/seatunnel Schedule Backend run 35244548330 (2026-09-17), *after* the previous widening in #12370: ``` [ERROR] PayPalClientTest.closeWakesRetryWait:416 expected: <true> but was: <false> ``` Line 416 is `assertTrue(arrived.await(...))` — the worker thread's **first** loopback request never reached the embedded `HttpServer` within 15s. Arrival is an environmental wait (worker thread start plus the OS loopback round trip on a stalled runner), not a client behavior, so it now uses a dedicated 60s `ARRIVAL_WAIT_SECONDS`. The close/cancel bounds stay at 15s so a genuine hang in the client's close wiring still fails the test quickly; common-case runtime is unchanged (milliseconds). **2. `FileCollectReaderBehaviorTest.rediscoversFileAfterInactiveCursorClosed` (Windows)** Known flaky on Windows runners (recorded across several fork CI runs). The test choreographs against a 500ms idle-close window and real filesystem glob scans, but capped every await at 3s — almost no margin if the runner is descheduled for a few seconds. Raise the await ceiling to 10s via a shared constant; the common case still finishes sub-second. ### Does this PR introduce any user-facing interface change? No. ### Verification - `./mvnw test -Dtest=PayPalClientTest` — 23/23 pass. - `./mvnw test -Dtest=FileCollectReaderBehaviorTest` — 3/3 pass. - `spotless:apply` clean for both modules. -- 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]
