SEPURI-SAI-KRISHNA commented on PR #12650:
URL: https://github.com/apache/seatunnel/pull/12650#issuecomment-6056523261
Build triage for `d928cd54d`, since the badge is red and none of it is this
change.
Run `37641679675`: 59 success, 1 failure, 2 cancelled, 23 skipped.
**`unit-test (8, ubuntu-latest)`, the only real failure.** One error in
`seatunnel-engine`:
```
JobMetricsTest>AbstractSeaTunnelServerTest.before:70 ยป IllegalState Node
faile...
Tests run: 561, Failures: 0, Errors: 1, Skipped: 5
```
It fails in setup, not in a test body. The Hazelcast member at
`[127.0.0.1]:18062` could not join the one at `:18081`:
```
Removing connection to endpoint [127.0.0.1]:18081 Cause => Unknown,
Error-Count: 11
[127.0.0.1]:18081 is added to the blacklist.
Could not join cluster. Shutting down now!
```
That is a cluster-join timeout on the shared runner: `Time elapsed: 300.189
s` is Hazelcast's join wait, and the very next class, `JobHistoryServiceTest`,
brought a node up fine at `:12958`. The reactor then banned the downstream
modules, which is what turned the job red. 53.6 min against a 120 min limit, so
not a timeout of the job itself.
Not reachable from this PR: the diff is two files, both in
`connector-common`, and `seatunnel-engine` is not touched. More to the point,
on this exact leg:
```
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.093 s
- in ArrowToSeatunnelRowReaderTest
```
and `unit-test` passed on the other three legs, 8/windows, 11/ubuntu and
11/windows, so the new coverage is green on every leg that completed.
**`updated-modules-integration-test-part-6`, both legs, recorded as
cancelled.** 210.7 and 211.2 minutes against `timeout-minutes: 210`, so both
hit the job wall. GitHub records a timeout as cancelled.
I did not find an open issue for the `JobMetricsTest` join failure, so I am
reporting it here as triage rather than claiming it is a known flake. Happy to
file it separately if you would like it tracked.
--
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]
