Hi Abhishek!

Thank you for working on this release!


I’ve built the project on Ubuntu22 in debug and release modes.
I’ve checked the test failures Zoltan described. We’ve cleared those up
offline:

Most of them were just flaky, and small test failures corresponding to non
Ubuntu18 machines: minidump-test and curl_util.


I’ve built the Java client locally and ran the Java example successfully.
There was just one caveat, that now we have to put

com.stumbleupon.async into the example pom. But I don’t think this should
hold up the release.


I’ve also built and ran all the Python client tests, those were fine
(Ubuntu22 and Python3.8). Moreover verified locally the package install:
built the Python dist, and installed it into a clean venv, and ran the
Python example. This was also fine.

+1 from my end.


Thanks again for your continued effort on this release!


Best,
Marton

Zoltan Chovan <zcho...@cloudera.com.invalid> ezt írta (időpont: 2025. jún.
30., H, 13:34):

> Hi!
>
> Thanks for putting together this RC!
> To verify I executed the following steps:
>
> 1. checked out '1.18.0-RC1' tag
> 2. build the thirdparty dependencies
> 3. build both DEBUG and RELEASE C++ builds
> 4. ran the full tests suite, with slow tests enabled by
> 5. re-ran failed tests 2x
> 6. built the Java bits and ran the tests, re-ran the failed tests 2x
>
> For both debug and release builds I encountered failing tests, some were
> flaky, and some may be affected by local environmental peculiarities.
>
> Debug test failures:
> 251 - txn_manager-test (Failed) - timeout
> 350 - kudu-admin-test.5 (Failed)
> 469 - curl_util-test (Failed) - timeout
>
> Release test failures:
> 108 - alter_table-test (Failed) -
> ReplicatedAlterTableTest.AlterReplicationFactorWhileWriting - local env
> issue?
> 178 - open-readonly-fs-itest (Failed) -
> OpenReadonlyFsITest.TestWriteAndVerify
> 251 - txn_manager-test (Failed) - TxnManagerTest.BeginManyTransaction
> timeout
> 378 - tablet_server-stress-test (Failed) -
> EvictionPolicyTypes/TSStressTestWithEvictionPolicy.TestMTInserts
> 417 - maintenance_manager-test (Failed) -
> MaintenanceManagerTest.ComprehensiveTest
> 464 - minidump-test (Failed) - MinidumpDeathTest.TestRegisterAndDelete
> 469 - curl_util-test (Failed) - timeout
>
> Java tests
>
> org.apache.kudu.client.TestSecurity.testExternallyProvidedSubjectRefreshedExternally
> - failed
>
> More details of test failures can be found here:
>
> https://docs.google.com/document/d/1vvlx96fbMVYbNCst9uzgO7XhW0sjFW9GFbmxwF3jjqY/edit?usp=sharing
>
> The test OS is Ubuntu 22.04.
> While some of these test failures seem flaky, I haven't found them in the
> flaky dashboard, so I'd really like to see other people's testing results
> to confirm if this was environmental/setup problem or actual issues that
> need fixed (I unfortunately haven't had the time to RCA these yet)
>
> In light of these results my vote would be 0 (non-binding).
>
> Best regards,
> Zoltan
>
> On Thu, Jun 26, 2025 at 2:02 AM Abhishek Chennaka <achenn...@apache.org>
> wrote:
>
> > Hello Kudu devs!
> >
> > The Apache Kudu team is happy to announce the first release candidate for
> > Apache Kudu 1.18.0.
> >
> > Apache Kudu 1.18.0 is a minor release that offers many improvements and
> > fixes since Apache Kudu 1.17.1.
> >
> > This is a source-only release. The artifacts have been staged here:
> > https://dist.apache.org/repos/dist/dev/kudu/1.18.0-RC1
> >
> > Java convenience binaries in the form of a Maven repository are staged
> > here:
> > https://repository.apache.org/content/repositories/orgapachekudu-1125
> >
> > Linux (x86_64 and aarch64 platforms built on RHEL 8) and macOS (built on
> > Sonoma) test-only Kudu binary JAR artifacts are staged here:
> > https://repository.apache.org/content/repositories/orgapachekudu-1126
> >
> > It is tagged in Git as 1.18.0-RC1 and signed with my key (found in the
> KEYS
> > file below). Its commit hash is cdb87324cd31be738c03b6b0765ca9d8d65f2852
> > you can check it out from ASF Gitbox or the official GitHub mirror:
> >
> >
> https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=cdb87324cd31be738c03b6b0765ca9d8d65f2852
> > https://github.com/apache/kudu/releases/tag/1.18.0-RC1
> >
> > The KEYS file to verify the artifact and tag signatures can be found
> here:
> > https://dist.apache.org/repos/dist/release/kudu/KEYS
> >
> > The release notes can be found here:
> > https://github.com/apache/kudu/blob/1.18.0-RC1/docs/release_notes.adoc
> >
> > I'd suggest going through the release notes, building Kudu, and running
> the
> > unit tests. Testing out the Maven repo would also be appreciated. Also,
> > it's worth running Kudu Java tests against kudu-binary JAR artifact as
> > described in the commit message here:
> >
> >
> https://github.com/apache/kudu/commit/8a6faaa93f3e206ac75e8087731daccaf7ab646a
> >
> > The vote will run until a majority[1] is achieved, but at least until
> > Saturday June 28 12:00:00 UTC 2025.
> >
> > Thank You,
> > Abhishek Chennaka
> >
> > [1] https://www.apache.org/foundation/voting.html#ReleaseVotes
> >
>

Reply via email to