sharpca commented on PR #13083:
URL: https://github.com/apache/seatunnel/pull/13083#issuecomment-6645011810
Status on the CI gate, with the pattern across four runs on these two heads.
Every failure so far is a container/network failure in a module this PR does
not touch, and none of them is the assertion this PR adds.
| Run | Head | Result | Failing job | Test |
| --- | --- | --- | --- | --- |
| 41730993933 | de80d16 | cancelled | part-8, doris-connector-it |
`MetalakeIT.startUp` ConditionTimeout; doris IT step |
| 41785714303 | de80d16 | failure | part-6 (17) | `TiDBCDCIT`
`CommunicationsException` / `EOFException` |
| 41880443702 | de80d16 | failure | part-7 (17) | `JdbcHanaIT` ERROR after
632s (`connector-jdbc-e2e-part-6`) |
| 41785719208 | cac71da | failure | unit-test (17), all-connectors-it-5 (17)
| `BindException: Address already in use`; Hive metastore `Connection refused` |
| 41881173697 | cac71da | failure | all-connectors-it-5 (17) | `TiDBCDCIT`
ERROR (`connector-cdc-tidb-e2e`) |
The positive side is unchanged and is the part that matters for review: on
de80d16 the shard that runs this PR's IT reports
JdbcMysqlSplitIT.testFixedStringSplitBoundsAreLocaleIndependent
successfully run
Tests run: 110, Failures: 0, Errors: 1
with the single error being `MetalakeIT`'s container timeout. In the two
latest runs the JDBC e2e module either passed or did not contain
`JdbcMysqlSplitIT` in the failing log at all - the red jobs were HANA and TiDB
CDC containers.
I am not going to keep re-running until a lucky green: each attempt costs
5-6 hours and lands on a different flaky container test. If you are willing to
weigh the code-level evidence above, the PR is one merge away; if you would
rather have a green run on the head, tell me and I will keep retrying, but I
would be spending your CI minutes on infrastructure, not on this change.
--
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]
