corgy-w commented on PR #12440: URL: https://github.com/apache/seatunnel/pull/12440#issuecomment-5781131834
Update on the Windows unit test job: the re-run (attempt 2) failed again, so I checked whether the failure is in this module. It is not. `connector-hudi` (module 44/310 of the Windows JDK 11 run, attempt 2): ``` Tests run: 3, Failures: 0, Errors: 0, Skipped: 0 - in ...hudi.config.HudiSinkConfigTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 1 - in ...hudi.catalog.HudiCatalogTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 - in ...hudi.HudiErrorTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 1 - in ...hudi.HudiTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 1 - in ...hudi.HudiTwoPhaseCommitTest (@DisabledOnOs(OS.WINDOWS)) Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 - in ...hudi.sink.commit.HudiSinkAggregatedCommitterTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0 - in ...hudi.sink.writer.HudiSinkWriterTest ``` The build failed later in the reactor: the part of the log that could be retrieved (up to module 98/310) contains no failure, and the `connector-http-*` modules, where the attempt 1 failure was (`PayPalClientTest#closeWakesRetryWait`), are at module 124 and above. That job runs the unit tests of all 310 modules, so any stall-sensitive test of the repository can turn it red regardless of the changed module. I started a third attempt of that job; the changed-modules integration test jobs of this PR (which include `connector-hudi-e2e`) are green. -- 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]
