DanielLeens commented on PR #12900: URL: https://github.com/apache/seatunnel/pull/12900#issuecomment-6359863530
Thanks for the detailed CI update, @hutiefang76, and for confirming from the checkout SHA and the target-case logs that `KafkaIT.testKafkaAvroNullableRowRoundTrip` and `PulsarFormatIT.testPulsarAvroNullableRowRoundTrip` actually executed on `132771ef9d1a` (JDK 17). That closes the main E2E evidence gap from my last review. I also checked the rest of that fork Build run (39772092860) on the same head. Every job completed as success or skipped except one: [`connector-file-local-it (17, ubuntu-latest)`](https://github.com/hutiefang76/seatunnel/actions/runs/39772092860/job/119803028876), which was cancelled when it hit the two-hour job limit (17:06 to 19:06 UTC). Its log was still running Spark parquet and binary file-local cases at that point. This PR does not touch `connector-file-local` or any parquet/file code (only the Avro format, Kafka, Pulsar and their docs/tests), so this is not caused by the diff. The overall `Build` check on the PR is reported as `timed_out` because of that one job. Minimal next step: please re-run only that failed job from the Actions page of your fork (for example `gh run rerun 39772092860 --repo hutiefang76/seatunnel --failed`, or the per-job rerun button). Please do not re-run the whole workflow and do not add unrelated patches. The `dev` divergence (ahead 4 / behind 12) is metadata only, with no conflict reported, so a sync is not needed for this. My source-level conclusion is unchanged: no blocking source issue, with the schema-reuse work staying in #12940. Once that job passes, I will recheck the Build state for this head and update my conclusion; final approval still needs a committer. Static analysis only; nothing was executed locally. -- 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]
