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

   Quick CI follow-up on `898d48a9`: the fork 
[Build](https://github.com/goutamadwant/seatunnel/actions/runs/42767235465) has 
finished. None of the failures come from this PR's changes. The new 
`RestSubmitJobVariablesIT` (in `engine-v2-it`) and the core-starter / 
engine-server unit tests passed on both JDKs.
   
   - `connector-file-sftp-it` 
[(11)](https://github.com/goutamadwant/seatunnel/actions/runs/42767235465/job/129929794950)
 / 
[(17)](https://github.com/goutamadwant/seatunnel/actions/runs/42767235465/job/129929794612):
 `SftpFileIT` can't pull `atmoz/sftp:alpine-3.7`. As mentioned in my review, 
that tag was removed, and #13203 on `dev` fixes it. A re-run won't help.
   - `all-connectors-it-5` 
[(11)](https://github.com/goutamadwant/seatunnel/actions/runs/42767235465/job/129929794306)
 / 
[(17)](https://github.com/goutamadwant/seatunnel/actions/runs/42767235465/job/129929793582):
 `TiDBCDCIT.startUp` fails with `Communications link failure` while the TiDB 
container starts. This is environmental, and this PR doesn't touch TiDB.
   - [`unit-test (11, 
ubuntu)`](https://github.com/goutamadwant/seatunnel/actions/runs/42767235465/job/129929793591):
 `SeaTunnelClientTest.testSetJobIdDuplicate` failed. This PR doesn't touch the 
client submit path or the duplicate-job-id check, and the same suite passed on 
the other three unit-test jobs. I believe it is unrelated, but I have not 
reproduced it locally.
   - [`all-connectors-it-2 
(11)`](https://github.com/goutamadwant/seatunnel/actions/runs/42767235465/job/129929793057):
 the hosted runner lost communication with the server. This is an 
infrastructure problem.
   
   Smallest next step: merge the latest `dev` (it is 3 commits ahead, including 
#13203). The new push re-runs everything, which also covers the flaky jobs. I 
will approve once that run is green.


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