DanielLeens commented on PR #12943: URL: https://github.com/apache/seatunnel/pull/12943#issuecomment-6783305634
Quick CI follow-up on `16714019`: the fork [Build](https://github.com/goutamadwant/seatunnel/actions/runs/42765842651) has finished and has one failure, in this PR's own new test. - [`engine-resource-managers-it (17)`](https://github.com/goutamadwant/seatunnel/actions/runs/42765842651/job/129705577600): `KubernetesApplicationHaIT.masterPodLossKeepsNativeJobAndFixedWorkers{boolean}[2]` (the `loseActive=true` case) timed out after 3 minutes in the Awaitility block at line 393. The probe could not reconnect to the cluster after the active master Pod was deleted (`Unable to connect to any cluster`). - The same job passed on JDK 11 for this head, and both JDKs passed on `4504ff81` and `713de07d`. Your diff has not changed since then (this head only merges `dev`), so this looks like an intermittent timing failure, not a code regression. I have not reproduced it locally. - No `dev` sync is needed: the SFTP job was skipped by change detection on this PR. Smallest next step: please re-run the failed job. If it fails again in the same place, the 180s recovery wait for the active-master case is probably too tight on CI. Since this is a new HA test, a flaky result here would also show up on `dev` after merge, so it is worth checking. My source review is unchanged: no blocker from my side, and @nzw921rx's change request still needs to be resolved. -- 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]
