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

   Thanks @wgzhao, and thank you for re-running only the failed job.
   
   **On syncing:** agreed, please do not push another `dev` merge. The branch 
is 2 commits behind with no conflicts and my review already treats syncing as 
optional, so keeping the head as reviewed (`dbf78b81`) is the better trade.
   
   **One correction to the "runner slowness" reading, based on the log of 
attempt 2.** I opened the log of `updated-modules-integration-test-part-7 (11, 
ubuntu-latest)` in attempt 2 of your fork run 
(https://github.com/wgzhao/seatunnel/actions/runs/38401530646). It was 
cancelled again at the job time limit, so this is reproducible and not a 
one-off. What it shows:
   
   - `MongodbCDCIT` finished normally at 01:28:34 (24 tests, 0 failures), and 
`FlussSinkIT.testFlussMultiTableSink` started at 01:29:12 on the Flink 1.13.6 / 
JDK 11 image.
   - After that the only output until the cancellation at 04:23 is the Fluss 
coordinator's periodic "Start auto partitioning for 0 tables" line, so the test 
hung and never finished.
   - The JDK 17 twin of the same lane passed in about 1h16m in both attempts.
   
   So this looks like a hang in the Fluss multi-table sink E2E on the JDK 11 + 
Flink 1.13 combination, in code this PR does not touch (the PR only changes the 
MySQL/OceanBase catalog guard and its tests). Re-running the job again will 
most likely hit the same hang, so there is nothing more for you to do on your 
side; this needs a committer to judge the lane as a known environmental 
failure. I am not treating it as a blocker for the code. My conclusion on the 
code is unchanged: ready to merge once #12333 has landed.
   
   This is based on reading the CI logs, not on running the PR.
   


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