nzw921rx commented on PR #11766: URL: https://github.com/apache/seatunnel/pull/11766#issuecomment-5299634750
> Thanks @nzw921rx โ on the CI condition: the one red job is unrelated to this change, and I've kicked off a re-run of it. > > `Run / unit-test (11, windows-latest)` was the only failure out of **85 jobs**, and it failed in test _setup_, not in an assertion: > > ``` > [ERROR] FollowerRunningJobsFilterTest>AbstractSeaTunnelServerTest.before:70 ยป IllegalState > java.lang.IllegalStateException: Node failed to start! > Time elapsed: 311.259 s > [ERROR] Tests run: 345, Failures: 0, Errors: 1, Skipped: 20 > ``` > > That is a Hazelcast member failing to come up on the Windows runner after five minutes, in `seatunnel-engine-server`. This PR's diff is two files in `seatunnel-core-starter` and cannot reach that module. > > The module this PR does touch passed on that very same Windows run: > > ``` > [INFO] Running org.apache.seatunnel.core.starter.flowcontrol.FlowControlGateTest > [INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 37.105 s > ``` > > So the five cases โ the three pre-existing timing tests plus the two zero-byte ones added here โ are green on Linux and on Windows. I'll report back once the re-run finishes. Hello, you can just rerun the failed CI jobs. -- 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]
