sharpca commented on PR #13170:
URL: https://github.com/apache/seatunnel/pull/13170#issuecomment-6760005924

   Hi @DanielLeens, thanks for the re-review. The merge conflict is resolved 
and `dev` is synced.
   
   **Conflict resolution** — merge of `dev` (`535d4237d`) into this branch, 
commit `89e3aa1ef`:
   
   - `docs/en/introduction/concepts/incompatible-changes.md` and 
`docs/zh/introduction/concepts/incompatible-changes.md`: both entries are kept 
— the Lance `BIGINT` entry from #13061 and the API locale entry from this PR. 
No production code was touched by the merge.
   - The diff against `dev` is now exactly: `PluginIdentifier`, 
`MetaLakeFactory`, `MetalakeConfigUtils`, `GravitinoTableSchemaConvertor`, the 
three test classes, and +7 lines in each of the two `incompatible-changes.md` 
files.
   
   **Local verification** (JDK 11, Maven 3.9.9):
   
   - `spotless:check` is clean.
   - `seatunnel-api` module: 416 tests run, 0 failures, 0 errors.
   
   **CI** on this head: the fork `Build` run 
[42736298199](https://github.com/sharpca/seatunnel/actions/runs/42736298199) 
finished with 79 jobs successful and 11 skipped. `Code style`, `License 
header`, `Dependency licenses` and all four unit-test jobs (JDK 11/17, 
Ubuntu/Windows) are green.
   
   The three red jobs are the same environmental ones you saw on the previous 
head — `connector-file-sftp-it` (11 and 17), where the `atmoz/sftp:alpine-3.7` 
image is no longer available, and `all-connectors-it-6` with the Hive metastore 
`TTransportException`. As you suggested, I re-ran the failed jobs, which is 
attempt 2 of the same run; it is in progress now.
   
   The apache-side `PR signal` run for this head is still waiting for approval, 
as on the previous heads.
   
   Thanks again!
   


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