corgy-w commented on PR #12440:
URL: https://github.com/apache/seatunnel/pull/12440#issuecomment-6118339177

   CI is green again on the head that contains the review fixes (`393edcfcb9`):
   
   **Run:** https://github.com/corgy-w/seatunnel/actions/runs/38163500699 — 
`completed/success`, no failed job
   
   | Job | Result |
   | --- | --- |
   | `unit-test` (11 / 17 × ubuntu-latest / windows-latest) | success |
   | `updated-modules-integration-test-part-1` (11 / 17) | success — the part 
that runs `connector-hudi-e2e` |
   | `Code style`, `License header`, `Dead links`, `changes`, `Sanity check 
results`, `Check Helm Chart`, `Build website` | success |
   
   The new exactly-once e2e case passes on both engines again after the review 
fixes:
   
   ```
   Test 
org.apache.seatunnel.e2e.connector.hudi.HudiIT.testWriteHudiWithExactlyOnceSemantics
 is running.
   [TimingExtension] [HudiIT#testWriteHudiWithExactlyOnceSemantics] E2E test 
case cost 26s.
   Test 
org.apache.seatunnel.e2e.connector.hudi.HudiIT.testWriteHudiWithExactlyOnceSemantics
 successfully run.
   ... second engine ... cost 23s ... successfully run.
   
   Tests run: 6, Failures: 0, Errors: 0, Skipped: 0 - in 
org.apache.seatunnel.e2e.connector.hudi.HudiIT
   Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 - in 
org.apache.seatunnel.e2e.connector.hudi.HudiSinkCDCIT
   Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 - in 
org.apache.seatunnel.e2e.connector.hudi.HudiMultiTableIT
   Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 - in 
org.apache.seatunnel.e2e.connector.hudi.HudiSparkS3MultiTableIT
   Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 - in 
org.apache.seatunnel.e2e.connector.hudi.HudiSeatunnelS3MultiTableIT
   ```
   
   Local verification of the same head (JDK 11): `spotless:apply` clean, 
`./mvnw -o -pl seatunnel-connectors-v2/connector-hudi test -DforkCount=0` → 
BUILD SUCCESS, 25 tests, 0 failures.
   


-- 
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]

Reply via email to