SEPURI-SAI-KRISHNA commented on PR #12182:
URL: https://github.com/apache/seatunnel/pull/12182#issuecomment-5595397760

   CI update. The rerun cleared one job and reproduced the other.
   
   `engine-v2-it (11, ubuntu-latest)` passed on rerun, confirming the 
`SinkErrorToMysqlIT` Awaitility timeout was environmental. `kudu-connector-it 
(8, ubuntu-latest)` also cleared. The only remaining failure is 
`transform-v2-it-part-1 (11, ubuntu-latest)`, which failed again with the same 
`TestFilterRowKindIT.testFilterRowKindMultiTable:53 expected: <0> but was: <1>`.
   
   One clarification on the attempt-2 reading, since it affects how many times 
this has actually been seen. In attempt 2 only `engine-v2-it (11)` re-executed. 
The `transform-v2-it-part-1 (11)` entry in that attempt carries `started_at: 
2026-09-07T16:23:33Z` and `completed_at: 2026-09-07T17:41:07Z`, which are 
attempt-1 timestamps: it was a carried-over record rather than a second run. My 
second job-level rerun had been rejected because attempt 2 was already in 
flight. So as of that point the flake had been observed once, not twice.
   
   It has now genuinely been observed twice, on attempt 3, job `102038075593`, 
which ran 11:09:32Z to 12:32:10Z. Interestingly it moved legs: attempt 1 failed 
on `{TestContainer}[3]`, `flink:1.18.0`, and attempt 3 on `{TestContainer}[2]`, 
`flink:1.15.3`. Both are legs #12116 already documents, and in both runs the 
Zeta and Spark legs and the JDK 8 leg of the same job passed. I have added both 
occurrences to #12116, since a single unchanged commit reproducing across 
reruns and moving between Flink versions is useful evidence for the 
shared-static-counter diagnosis there.
   
   Practically that means a rerun is not a reliable way to get this check 
green: two executions of that job on this head, two failures. The unit test 
legs, which are what actually exercise this change, are green throughout.
   
   @davidzollo this is ready from my side whenever you have time. Since #12116 
is yours, you will know better than me whether it is worth waiting for a green 
`Build` here or treating the `TestFilterRowKindIT` leg as known-red.
   


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