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

   Thanks @SEZ9 and @hutiefang76. I took a look at the fork run 
(https://github.com/hutiefang76/seatunnel/actions/runs/39775915510) for 
`ef53a70c6f72f5f6ae7c31fcc57b541eb3c849f3`, as a snapshot of right now. It is 
still `in_progress` (at least `all-connectors-it-6 (11)` has not finished), so 
there is no final result yet. Two jobs have already failed, and neither failure 
points at `SeaTunnelRow`:
   
   - `unit-test (11, ubuntu-latest)` 
([job](https://github.com/hutiefang76/seatunnel/actions/runs/39775915510/job/119919173849)):
 Maven failed while resolving `seatunnel-translation-flink-20`, with `Could not 
transfer artifact org.apache.flink:flink-rpc-akka-loader:jar:1.20.1 from/to 
central ... Connection reset`. That is a dependency-download network error, not 
a test failure. The 17/ubuntu, 17/windows and 11/windows unit-test jobs passed.
   - `engine-v2-it (11, ubuntu-latest)` 
([job](https://github.com/hutiefang76/seatunnel/actions/runs/39775915510/job/119919175848)):
 
`BackpressureSlowSinkIT.testCheckpointsKeepCompletingUnderSustainedBackpressure`
 timed out in an Awaitility wait ("within 2 minutes", 
`BackpressureSlowSinkIT.java:184`). This is a checkpoint/backpressure timing 
test in the Zeta engine E2E suite. The same job on JDK 17 passed. This is an 
assessment from the logs, not something I reproduced.
   
   Suggested next step, @hutiefang76: once the run finishes, please re-run only 
the failed jobs from the Actions page ("Re-run failed jobs") and post the final 
outcome here. No source change is needed for either failure. If 
`BackpressureSlowSinkIT` fails again on the same head, please link that run and 
we can look at it more closely.
   
   The expectation I set earlier still holds: a `workflow_dispatch` run is 
evidence for this exact commit, but it does not replace the PR-bound `Build` 
check, so a maintainer retry of the failed `Notify test workflow` is still 
needed. My source-level conclusion is unchanged: no source-side blocker.


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