prashantwason commented on PR #18904:
URL: https://github.com/apache/hudi/pull/18904#issuecomment-4633738190
CI on `165a2fce` is green except for two unrelated, pre-existing flaky jobs:
- **`test-spark-java17-java-tests-part2 (spark4.1)`** — FAILURE:
-
`TestHoodieClientMultiWriter.testHoodieClientBasicMultiWriterWithEarlyConflictDetectionDirect[3]`
— first attempt failed with a transient `SparkException: Lost task ...
HoodieUpsertException` on an executor, and the retries then failed with `Unable
to instantiate class
org.apache.hudi.client.transaction.lock.ZookeeperBasedLockProvider` (ZooKeeper
connectivity). This test has a known flaky history (see #17793 "Fix flaky test
in TestHoodieClientMultiWriter"). surefire also reported `Flakes: 1` for this
run.
- `TestHoodieIndex.testTagLocationDuringUpdatesAndFailures[7]` — transient
`Failed to upsert for commit time ...`.
- **`test-spark-java17-java-tests-part2 (spark4.0)`** — CANCELLED (fail-fast
collateral from the spark4.1 job).
None of these touch `HoodieHeartbeatClient` or the heartbeat config changed
in this PR (the failures are in the ZK lock-provider and upsert code paths).
The job this PR's change is actually relevant to —
`test-hudi-hadoop-mr-and-hudi-java-client` — passes.
Could a committer please re-run the two failed
`test-spark-java17-java-tests-part2` jobs? Thanks!
--
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]
