SEZ9 commented on PR #12984:
URL: https://github.com/apache/seatunnel/pull/12984#issuecomment-7025810626

   Following up on the CI status for 
`fd0c32bc64ea4eeacd736767d0176f41c9377345`, which has not changed since the 
last review.
   
   **Current state**
   - Fork Build 42347729501 has completed with a failure, so no queued retry is 
outstanding.
   - The Apache Build still reports failure on the same head.
   - This is a CI clarification only. The earlier source-scope concern stays 
open, and nothing here shows that the SQS, Kafka or engine validation passed.
   
   **What is known about the failures** (from @davidzollo's update on attempt 2)
   - **Amazon SQS job (128821435185):** failed before assertions because 
LocalStack could not start (`/testcontainers_start.sh: Text file busy`).
   - **Kafka job (128821435460):** failed a committed-offset assertion.
   - **Engine job (128821435114):** observed FAILED instead of CANCELED.
   
   The SQS fixture failure does not explain the other two. The Kafka and engine 
results are assertion failures and cannot be written off as infrastructure 
without attribution.
   
   **Remaining asks before any further retry**
   1. Inspect the completed attempt and post which jobs failed in it. The 
thread only details attempt 2, so please confirm whether the final attempt 
shows the same three failures.
   2. Attribute the Kafka committed-offset failure and the engine 
FAILED/CANCELED result by reconciling them against the current 
`SourceCheckpointLockHandoff` / `SourceFlowLifeCycle` paths.
   3. Show the effective diff of this head against `dev`, as already requested.
   4. Retry only the specific jobs that this diagnosis justifies. Please do not 
add unrelated dependency changes or rely on a sync-only push to turn the run 
green.
   
   The existing source/validation checklist stays open, and an independent 
maintainer review is still required before this can move forward.
   
   <!-- streview-comment:2473 -->


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