tchivs commented on PR #4530:
URL: https://github.com/apache/flink-cdc/pull/4530#issuecomment-5616779920
CI came back on 2e37478: **18 of 19 checks green**, and every case that this
PR actually broke now passes.
- `Pipeline Unit Tests` and `Pipeline Connectors Unit Tests 2.x` are green,
so `PostgresFullTypesITCase` is fixed on both Flink lines.
- `Pipeline E2E Tests (1-Parallelism)`, `Pipeline E2E Tests 2.x
(1-Parallelism)` and `Pipeline E2E Tests 2.x (4-Parallelism)` are green.
- Only `Pipeline E2E Tests (4-Parallelism) / test (11, 1.20.3,
pipeline_e2e)` is red, and `TransformE2eITCase` reports `Tests run: 24,
Failures: 0, Errors: 1` there — no assertion failure, so
`testTemporalFunctions` passed in that job too.
The two remaining failures look unrelated to TIME:
1. `TransformE2eITCase#testAssortedSchemaTransform(boolean)[1]` —
`TimeoutException: failed to get specific event:
CreateTableEvent{tableId=transform_test_duaf6z.terminus, schema=columns={ID INT
NOT NULL, VERSION STRING, NAME STRING}, ...}`. No temporal column is involved;
the job simply did not reach that event inside the timeout.
2. `MySqlToIcebergE2eITCase#testSyncWholeDatabase` — the collected rows
still had 10 fields while the expectation has 16 (`..., 1, 1, 1, 1, 1, 1, 1, 1,
1, 1`), i.e. the assertion ran before the added columns had propagated. Again
no TIME column in the diff.
Both are in the 4-parallelism `1.20.3` job only, and that job flakes on
`master` as well, independently of this PR: nightly run `34072345338`
(2026-09-07) failed the same job on
`MySqlToHudiE2eITCase#testSyncWholeDatabase`, and run `33935167454`
(2026-09-05) failed the 1- and 4-parallelism E2E jobs.
I cannot re-run it myself (`Must have admin rights to Repository`).
@yuxiqian could you kick off a re-run of that single job when you get a chance?
If you would rather see a fresh full run, I can push a no-op commit instead —
just say which you prefer.
--
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]
