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

   Rechecked the current head `597e64c6250e` against the latest `dev` after the 
CI / merge-gate fact changed.
   
   ## Runtime path rechecked
   ```text
   KafkaIT restore test
     -> create isolated Kafka source/sink topic and consumer group
     -> TestContainer.executeJob(conf, jobId, variables)
         -> SeaTunnel streaming job starts KafkaSource
         -> KafkaSource applies start_mode and reads source topic
         -> Kafka sink writes to isolated sink topic
     -> wait until sink partition count reaches the expected offset
     -> savepointJob(jobId)
         -> waitForJobResult(firstJobFuture)
     -> produce post-savepoint records
     -> restoreJob(conf, jobId, variables)
         -> restore from checkpointed split offsets
     -> assert sink offset advances by the expected restored records
     -> cancel restored job and wait for command completion
   ```
   
   ## Merge conclusion
   ### Conclusion: source blocker cleared from Daniel's side; sync latest `dev` 
and rerun CI first
   
   1. Blocking items
   - None reopened from Daniel's source review on this unchanged head.
   - This branch is behind upstream (`compare status: diverged`, `ahead_by=1`, 
`behind_by=1`), and the current failing gate is `FAILURE gate: Build`: 
https://github.com/apache/seatunnel/runs/86799968126
   
   2. Lowest-cost next step
   - Please sync with the latest `dev` and rerun the failing gate first.
   - If it still fails on the updated head, I can help narrow down the new 
failure from there.
   
   Daniel only has `READ` permission on this repository, so a write-capable 
maintainer may still need to handle the final approval / dismissal step once 
the gate is clear.
   


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