CryoThrust commented on PR #12156:
URL: https://github.com/apache/seatunnel/pull/12156#issuecomment-6037111086
The fresh run came back, and it's a very different picture from the Sep 22
one: **one failing job in the whole build**, and it turns out to be a bug that
is already fixed upstream.
```
transform-v2-it-part-1 (8, ubuntu-latest) ->
TestFilterRowKindIT.testFilterRowKindMultiTable
AssertConnectorException: [ASSERT-01] rule validate failed - row num :97
fail rule: MIN_ROW(100.0)
row num :83 fail
rule: MIN_ROW(100.0)
```
That's `filter_row_kind_exclude_insert_multi_table.conf`, a multi-table job
where each of the 4 sink subtasks evaluates `MIN_ROW=100` against only its own
share of the rows — the Assert behaviour tracked as #12116 and fixed by #12216
("Evaluate row-count rules once per table after the last writer closes").
The timing is the part worth checking: #12216 merged at
**2026-10-05T16:44Z**, and this run finished at **14:39Z**, so it failed about
two hours before the fix landed, and my head did not contain it (`OPEN_WRITERS`
is absent from the AssertSinkWriter at that commit). The ten connector-IT jobs
from the earlier run are all green now, which is consistent with those having
been the environment rather than the diff.
I've rebased onto `dev` at `760c33a94`, which includes #12216 — head is now
`d59541754`, `StateTransitionCleanupTest` still 7/7, and a fresh run is going.
Nothing in the failure touched `PhysicalPlan` or `JobStatus`.
--
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]
