SEPURI-SAI-KRISHNA commented on PR #19652:
URL: https://github.com/apache/hudi/pull/19652#issuecomment-5322885226
Thanks for the review! On CI: the only failure is pre-existing on master and
unrelated to this PR.
The run is 525 of 526 green, failing solely on:
```
TestValidateHoodieSyncProcedure > "Test Call sync_validate record-count
modes fail fast on an unreachable HiveServer2"
causeChain(latestPartitionsFailure).exists(_.isInstanceOf[java.sql.SQLException])
was false
java.lang.NoClassDefFoundError
(TestValidateHoodieSyncProcedure.scala:250)
```
Evidence that it is not this change:
- The same single test fails on all three of my open PRs, which touch
unrelated code: #19646 (`DataSkippingUtils`), #19648
(`PartitionPathFormatterBase`), #19652 (`HoodieSparkUtils`) — builds 16336,
16342 and 16345 respectively, each 525/526.
- It reproduces on a local dev machine with no CI resource pressure: running
that suite alone gives `Tests: succeeded 5, failed 1` with the identical
assertion and `NoClassDefFoundError`. So it is deterministic, not an
agent/memory flake.
- `TestValidateHoodieSyncProcedure` was added by #19161 (merged 2026-08-14).
Azure builds each PR's own branch, so PRs branched before that date do not
contain the test and are green — e.g. #19644, build 16334, succeeded. Every
branch cut from master after #19161 inherits the failure.
The test asserts the Hive JDBC driver surfaces a `SQLException` for
`jdbc:hive2://unused`, but the whole cause chain is a bare
`NoClassDefFoundError`, so some class the Hive JDBC path needs is not loadable
in that test context. `chainTypes` prints only class names, so the missing
class name is not in the output.
Happy to rebase, or to open a separate issue/PR for the broken test if that
is the preferred way to unblock — just let me know.
--
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]
