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

   Thanks @CryoThrust for the precise run and test-report details. My earlier 
statement that no fork Build had executed is now stale: [this 
Build](https://github.com/CryoThrust/seatunnel/actions/runs/43151029739) 
executed and failed in SFTP E2E (JDK 11/17) and engine E2E (JDK 11).
   
   For SFTP, the image-tag repair is already merged in `dev` as #13203 
(`379292194cc9ee9ecba2f6adf07cefcc94a7db21`), changing `SftpFileIT.java:70` 
from `atmoz/sftp:alpine-3.7` to `atmoz/sftp:alpine`. Please sync latest `dev` 
and rerun Build; no competing image fix is needed in this PR.
   
   The engine lane is a separate gate. Your artifact reports 
`BackpressureSlowSinkIT#testCheckpointsKeepCompletingUnderSustainedBackpressure`
 observing only two additional checkpoints within its 90-second window. I 
independently confirmed that the engine job failed, but have not independently 
extracted that test report. The SFTP fix does not establish that this 
checkpoint test is fixed. Keep its failure visible on the rerun and attach the 
new test report if it persists; do not weaken the checkpoint assertion or add 
unrelated changes to this CLI PR merely to obtain green CI.
   
   My prior source conclusion remains clear for the reviewed CLI scope. The 
Build remains failed, so this is a correction of the CI guidance, not approval.
   
   Recorded comparison: unchanged head 
`55831abaef1e1aac58988977c1da8e73a27d9417`, base `dev`, `diverged`, ahead 6 / 
behind 142. The sync recommendation is tied specifically to the verified 
upstream SFTP fix. No local runtime tests were executed.


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