SEPURI-SAI-KRISHNA commented on PR #12605:
URL: https://github.com/apache/seatunnel/pull/12605#issuecomment-6074462838
Build triage for `be3a828cf`, since the badge is red and none of it is this
change.
Run `37750462260`: 80 success, 2 failure, 1 cancelled, 11 skipped.
**`engine-v2-it` on both legs: the same known flake.** From the test-report
artifacts of each leg, one failure apiece and nothing else:
```text
BackpressureSlowSinkIT.testCheckpointsKeepCompletingUnderSustainedBackpressure
(8) expected at least 3 additional checkpoints ... only observed 2
(samples=[1, 1, 2, 2, 3, 3, 3, 3, ...])
(11) expected at least 3 additional checkpoints ... only observed 2
(samples=[1, 1, 2, 2, 2, 2, 3, 3, ...])
```
That is #12313 and #12316, both open. 102.7 and 94.0 minutes against a 150
minute limit, so neither is a timeout; they are genuine recurrences of the
flake.
**`Build website` is the 90 minute wall**, not a failure: 90.4 minutes
against `timeout-minutes: 90`, which GitHub records as cancelled. #12614 fixed
exactly this and is already in `dev`, so a rebase clears it.
**Not reachable from this PR.** The diff is `seatunnel-transforms-v2` plus
the docs note. `seatunnel-engine` is untouched, and the jobs that do exercise
this change all passed:
```text
unit-test success on all 4 legs (8/11 x ubuntu/windows)
transform-v2-it-part-1 success on both legs
transform-v2-it-part-2 success on both legs
```
So the new `SystemFunction` range check and the eighteen tests across
`ZetaSQLEngineTest` and `SystemFunctionTest` ran green everywhere they run.
I would rather rebase onto current `dev` than ask for a re-run: it removes
the `Build website` failure outright by picking up #12614, and leaves only the
known checkpoint flake to judge. Happy to do that whenever suits, or to leave
it if you would rather not churn an approved diff.
--
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]
