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

   ## What does this PR do?
   
   Two test-only changes to `connector-doris-e2e` for flakes that keep failing 
unrelated PRs' `doris-connector-it` jobs.
   
   ### 1. Container startup budget (`AbstractDorisIT`)
   
   `apache/doris:doris-all-in-one-2.1.0` was started with the 60 s default of 
Testcontainers' port wait strategy. The all-in-one image only opens the exposed 
ports once FE is up, which on loaded runners takes longer than that: `Timed out 
waiting for container port to open (localhost ports: [...] should be 
listening)` after ~61 s, while the JDBC readiness loop that follows the start 
would still have had five minutes (fork runs 33971836407 `doris-connector-it 
(8)` and 34002072283 `doris-connector-it (8)`, three ITs each). The port wait 
now gets the same six-minute budget as the readiness loop.
   
   ### 2. Wait for 2pc visibility (`DorisIT`)
   
   `assertHasData` and the row count in `testCustomSql` read the sink table 
exactly once, right after `executeJob` returned. The sink jobs run with 
`sink.enable-2pc = true`, so rows become visible only after Doris has published 
the committed transaction, and on the Spark legs that publish lagged the job 
exit: empty sink table in `testDoris` and `testDorisDirectToBe` (Spark 2.4 leg, 
runs 34004664286 and 34002072283) and 1 of 101 rows in `testCustomSql` (Spark 
3.3 leg, run 33994609465). Both checks now wait for visibility with Awaitility 
(60 s, 1 s poll). The assertions are unchanged; only the single read became a 
bounded wait.
   
   ## Does this PR introduce any user-facing change?
   
   No. Test-only.
   
   ## How was this patch tested?
   
   Test-only; validated by this PR's `doris-connector-it` jobs on both JDK legs.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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