SEPURI-SAI-KRISHNA commented on PR #12290:
URL: https://github.com/apache/seatunnel/pull/12290#issuecomment-5946777898
Rerun done, @SEZ9, and it is green. No new commit, same head `4d64a4d8`,
failed-jobs-only rerun of run `36725638109`.
Attempt 2: 83 jobs successful, 11 skipped, 0 failed. The upstream `Build`
check is now passing.
The three legs you asked about:
| leg | attempt 1 | attempt 2 |
| --- | --- | --- |
| `iceberg-connector-it (8)` | `DependencyResolutionException`, no test ran
| pass, dependencies resolved |
| `jdbc-connectors-it-part-7 (11)` | `MetalakeIT` error in `startUp` | pass |
| `transform-v2-it-part-1 (11)` | `TestFilterRowKindIT`, tracked by #12116 |
pass |
On `MetalakeIT` specifically, since that was the one worth a second data
point. It did not recur, and the timing says why:
```
attempt 1: Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 1,853.228 s
testMetalake Time elapsed: 1,219.394 s <<< ERROR!
ConditionTimeoutException ... expected: <0> but was: <7> within
3 minutes
at MetalakeIT.startUp(MetalakeIT.java:158)
attempt 2: Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 94.562 s
```
94 seconds against 1,853. The failure was the fixture never coming up inside
its three-minute window on a slow runner, not anything in the test or in this
change. One occurrence with no recurrence, so I am not filing it, as agreed. If
it shows up again I will sample the nightlies and open it with a proper sample
rather than two anecdotes.
Nothing else outstanding from my side.
--
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]
