DanielLeens commented on PR #12152:
URL: https://github.com/apache/seatunnel/pull/12152#issuecomment-5726053181

   Small correction to my own last comment: I said 
"connector-v2/transform-v2/rocketmq/engine-v2" from memory of the earlier 
rounds rather than pulling the actual job list for this run, and that undersold 
what's there. Pulling the real job list for the fork's run on `44f762eac` 
(`CryoThrust/seatunnel` run 35073705157), the failures are:
   
   - `all-connectors-it-1`, `all-connectors-it-2`, `all-connectors-it-7` (8/11)
   - `paimon-connector-it` (11), `rocketmq-connector-it` (11)
   - `engine-v2-it` (8)
   - `unit-test` (8/11, **windows-latest** only)
   
   No `transform-v2` failure on this run — that was me mis-citing an earlier 
round from memory, sorry. The connector/engine-it lanes are the same "doesn't 
touch `CheckpointCoordinator.java`" story as before. The windows `unit-test` 
failures are new to this run, but I checked the log rather than guess: it's 
`PayPalClientTest.closeWakesRetryWait` (`connector-http-paypal`), a known 
loopback-HTTP timing flake on Windows CI runners — already fixed on `dev` 
(widened wait budget), just not yet present on this branch's fork point. So all 
of it is still environmental/pre-existing, none of it touches this PR's diff. 
Doesn't change my conclusion — still ready to merge once a fresh run (post 
dev-sync) comes back clean.


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