I checked out the code on the 1.17.0-RC1 tag, and verified the tests including:

C++ code (on CentOS 7.9):
DEBUG version: all tests passed (hybrid_clock-test
--gtest_filter=HybridClockTest.TestNtpDiagnostics failed at the
beginning, then I installed and started ntp/chrony, then it passed)
ASAN version: all tests passed
TSAN version: all tests passed (except 'log-rolling-itest
--gtest_filter=LogRollingITest.TestLogCleanupOnStartup' with a data
race error, maybe we can skip the test as ASAN do[1]. It's just a
test, we can ignore it).

Java example (on macOS with Intel chips):
I got the same error as Yifan, the reason is the same.


@Marton Greber, have you installed the Kudu java client firstly?
My steps:
wget 
https://repository.apache.org/content/repositories/orgapachekudu-1104/org/apache/kudu/kudu-client/1.17.0/kudu-client-1.17.0.jar
mvn install:install-file -DgroupId=org.apache.kudu
-DartifactId=kudu-client -Dpackaging=jar -Dversion=1.17.0
-Dfile=./kudu-client-1.17.0.jar


1. 
https://github.com/apache/kudu/blob/branch-1.17.x/src/kudu/integration-tests/log-rolling-itest.cc#L57

Best regards,
Yingchun Lai


On Mon, Aug 7, 2023 at 6:13 PM Zhang Yifan <chinazhangyi...@163.com> wrote:
>
> Thanks for managing the 1.17.0 release, Yingchun!
>
> I checked out the code tagged with 1.17.0-RC1 and built c++
> components and tests successfully in RELEASE mode on a
> CentOS Linux release 7.9 (Final) server.
>
>
> All tests passed except for the following:
>   - hybrid_clock-test
>   - security-itest
> The failure of  hybrid_clock-test is:
> /data1/kudu/apache-kudu/src/kudu/clock/hybrid_clock-test.cc:501: Failure
> Value of: s.ToString()
> Expected: has substring "Error reading clock. Clock considered unsynchronized"
> Actual: "Service unavailable: timed out waiting for clock synchronisation: 
> wallclock is not synchronized: no valid NTP responses yet" (of type 
> std::string)
> Seems these issues are test-only and related to the running environment.
>
>
> I also tried to run the java-example test (using the command 'mvn package')
> after installing the kudu-client, kudu-test-util and the provided kudu-binary
> JAR artifact locally. I got the following error:
> [cluster stderr printer] INFO org.apache.kudu.test.cluster.MiniKuduCluster - 
> ERROR: unknown command line flag 'serialization'
>
>
> I guess this error is relate to the recent change[1] in the 
> tool-action-test.cc.
> When building Kudu with '-DNO_TESTS=1' the 'kudu' command no longer has
> the 'test' mode now. But we still build kudu binaries with '-DNO_TESTS=1' in
> build-support/mini_cluster/build_mini_cluster_binaries.sh.
>
>
> I'm not sure whether this issue should block the process for 1.17.0-RC1
> voting, considerring that the release is source-only and there is no problem
> with the core codebase except the script mentioned above. If not, I'm fine
> with +1 for this release candidate.
>
>
> [1] 
> https://github.com/apache/kudu/commit/176739729dd237230c40560a202ca7a82da8e088#diff-5c238a6f183a9a30d005adf4a6da7f8611e8a9e6c9329b7bae9ec7647e61ff6d
>
>
> 在 2023-08-05 18:47:30,"Marton Greber" <greber...@gmail.com> 写道:
> >[OSX arm tests]
> >
> >Macbook pro, M1, Ventura 13.5
> >
> >
> >*C++*
> >
> >DEBUG build:
> >
> >couple tests failed, but those match what is present in the macOS failed
> >tests tracking jira(KUDU-2715
> ><https://issues.apache.org/jira/browse/KUDU-2715>)
> >
> >Ran kudu perf loadgen:
> >
> >ran fine.
> >
> >
> >*Java example:*
> >
> >The convenience repository is missing for the aarch64 artefact. I’m happy
> >to help with this.
> >
> >After building the needed jars, and installing them locally(mvn
> >install:install-file), running the Java example gives the following error:
> >
> >*“Exception in thread "main" java.lang.NoClassDefFoundError:
> >com/stumbleupon/async/Callback*
> >
> >* at
> >org.apache.kudu.client.AsyncKuduClient$AsyncKuduClientBuilder.build(AsyncKuduClient.java:3112)*
> >
> >* at
> >org.apache.kudu.client.KuduClient$KuduClientBuilder.build(KuduClient.java:769)*
> >
> >* at org.apache.kudu.examples.Example.main(Example.java:184)*
> >
> >*Caused by: java.lang.ClassNotFoundException:
> >com.stumbleupon.async.Callback*
> >
> >* at java.net.URLClassLoader.findClass(URLClassLoader.java:382)*
> >
> >* at java.lang.ClassLoader.loadClass(ClassLoader.java:418)*
> >
> >* at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)*
> >
> >* at java.lang.ClassLoader.loadClass(ClassLoader.java:351)*
> >
> >* ... 3 more*
> >
> >*Process finished with exit code 1”*
> >
> >This happens both with the provided convenience jars, and the self-built
> >ones as well.
> >
> >Did anybody else try out the Java part? Was it working correctly? (Could
> >you please post the repro commands, just in case I was doing something
> >wrong)
> >
> >(the example was failing for me even on x86_64 linux.
> >
> >   1. built the java client
> >   2. installed the jars(mvn install:install-file)
> >   3. mvn package results in the following error, while it runs the test:
> >
> >*[main] INFO org.apache.kudu.test.cluster.KuduBinaryLocator - Using Kudu
> >binary jar directory: /tmp/kudu-binary-jar357889775327489877*
> >
> >*[main] INFO org.apache.kudu.test.cluster.MiniKuduCluster - Starting
> >process:
> >[/tmp/kudu-binary-jar357889775327489877/kudu-binary-1.17.0-linux-x86_64/bin/kudu,
> >test, mini_cluster, --serialization=pb]*
> >
> >*[cluster stderr printer] INFO org.apache.kudu.test.cluster.MiniKuduCluster
> >- ERROR: unknown command line flag 'serialization'*
> >
> >*[main] ERROR org.apache.kudu.test.junit.RetryRule -
> >org.apache.kudu.examples.ExampleTest.testCreateExampleTable: failed attempt
> >1*
> >
> >*java.io.EOFException*
> >
> >*        at java.io.DataInputStream.readInt(DataInputStream.java:392)*
> >
> >*        at
> >org.apache.kudu.test.cluster.MiniKuduCluster.sendRequestToCluster(MiniKuduCluster.java:191)*
> >
> >*        at
> >org.apache.kudu.test.cluster.MiniKuduCluster.start(MiniKuduCluster.java:262)*
> >
> >*        at
> >org.apache.kudu.test.cluster.MiniKuduCluster.access$300(MiniKuduCluster.java:85)*
> >
> >*        at
> >org.apache.kudu.test.cluster.MiniKuduCluster$MiniKuduClusterBuilder.build(MiniKuduCluster.java:883)*
> >
> >*        at
> >org.apache.kudu.test.KuduTestHarness.before(KuduTestHarness.java:156)*
> >
> >*        at
> >org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:50)*
> >
> >*        at
> >org.apache.kudu.test.junit.RetryRule$RetryStatement.doOneAttempt(RetryRule.java:225)*
> >
> >*        at
> >org.apache.kudu.test.junit.RetryRule$RetryStatement.evaluate(RetryRule.java:246)*
> >
> >*        at
> >org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)*
> >
> >*        at
> >org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)*
> >
> >*        at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)*
> >
> >*        at
> >org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)*
> >
> >*        at
> >org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)*
> >
> >*        at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)*
> >
> >*        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)*
> >
> >*        at
> >org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)*
> >
> >*        at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)*
> >
> >*        at
> >org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)*
> >
> >*        at
> >org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)*
> >
> >*        at org.junit.runners.ParentRunner.run(ParentRunner.java:413)*
> >
> >*        at
> >org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)*
> >
> >*        at
> >org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)*
> >
> >*        at
> >org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)*
> >
> >*        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
> >
> >*        at
> >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
> >
> >*        at
> >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
> >
> >*        at java.lang.reflect.Method.invoke(Method.java:498)*
> >
> >*        at
> >org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)*
> >
> >*        at
> >org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)*
> >
> >*        at
> >org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)*
> >
> >*        at
> >org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)*
> >
> >*        at
> >org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)*
> >
> >*[main] ERROR org.apache.kudu.test.junit.RetryRule -
> >org.apache.kudu.examples.ExampleTest.testCreateExampleTable: giving up
> >after 1 attempts*
> >
> >*Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.586 sec
> ><<< FAILURE!*
> >
> >*testCreateExampleTable(org.apache.kudu.examples.ExampleTest)  Time
> >elapsed: 0.562 sec  <<< ERROR!*
> >
> >*java.io.EOFException*
> >
> >*        at java.io.DataInputStream.readInt(DataInputStream.java:392)*
> >
> >*        at
> >org.apache.kudu.test.cluster.MiniKuduCluster.sendRequestToCluster(MiniKuduCluster.java:191)*
> >
> >*        at
> >org.apache.kudu.test.cluster.MiniKuduCluster.start(MiniKuduCluster.java:262)*
> >
> >*        at
> >org.apache.kudu.test.cluster.MiniKuduCluster.access$300(MiniKuduCluster.java:85)*
> >
> >*        at
> >org.apache.kudu.test.cluster.MiniKuduCluster$MiniKuduClusterBuilder.build(MiniKuduCluster.java:883)*
> >
> >*        at
> >org.apache.kudu.test.KuduTestHarness.before(KuduTestHarness.java:156)*
> >
> >*        at
> >org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:50)*
> >
> >*        at
> >org.apache.kudu.test.junit.RetryRule$RetryStatement.doOneAttempt(RetryRule.java:225)*
> >
> >*        at
> >org.apache.kudu.test.junit.RetryRule$RetryStatement.evaluate(RetryRule.java:246)*
> >
> >*        at
> >org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)*
> >
> >*        at
> >org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)*
> >
> >*        at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)*
> >
> >*        at
> >org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)*
> >
> >*        at
> >org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)*
> >
> >*        at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)*
> >
> >*        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)*
> >
> >*        at
> >org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)*
> >
> >*        at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)*
> >
> >*        at
> >org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)*
> >
> >*        at
> >org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)*
> >
> >*        at org.junit.runners.ParentRunner.run(ParentRunner.java:413)*
> >
> >*        at
> >org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)*
> >
> >*        at
> >org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)*
> >
> >*        at
> >org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)*
> >
> >*        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
> >
> >*        at
> >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
> >
> >*        at
> >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
> >
> >*        at java.lang.reflect.Method.invoke(Method.java:498)*
> >
> >*        at
> >org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)*
> >
> >*        at
> >org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)*
> >
> >*        at
> >org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)*
> >
> >*        at
> >org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)*
> >
> >*        at
> >org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)*
> >)
> >
> >
> >*Python*
> >
> >Everything was working fine:
> >
> >   - built python client lib,
> >   - ran all the tests
> >   - installed the lib locally
> >   - ran basic examples with the installed lib
> >
> >
> >After some more feedback/ruling out the java example issue, I’m fine with
> >+1 (non-committer).
> >
> >Thank you for all your efforts Yingchun!
> >
> >Mahesh Reddy <mre...@cloudera.com.invalid> ezt írta (időpont: 2023. aug.
> >4., P, 21:47):
> >
> >> +1 for the 1.17 release.
> >>
> >> I used the source artifacts staged here:
> >> https://dist.apache.org/repos/dist/dev/kudu/1.17.0-RC1
> >>
> >> I successfully built Kudu's C++ components and tests in the RELEASE
> >> configuration on CentOS Linux release 7.3.1611 (Core).
> >>
> >> All the tests passed except the following:
> >>     security-itest
> >>
> >> The scenarios within security-itest that failed involved RangerKMS as
> >> Alexey mentioned above.
> >>
> >> Thanks for taking care of this release Yingchun!
> >>
> >>
> >> On Thu, Aug 3, 2023 at 10:46 AM Alexey Serbin <aser...@cloudera.com.invalid
> >> >
> >> wrote:
> >>
> >> > Thank you for taking care of the release management for Kudu 1.17.0,
> >> > Yingchun!
> >> >
> >> > +1 for releasing Kudu 1.17.0 as per the information above.
> >> >
> >> > I verified the 1.17.0-RC1 tag is set on the 34243b3d0 changelist in the
> >> > upstream git repo.
> >> >
> >> > I did the following to verify the functionality of the new 1.17.0
> >> release:
> >> > * checked out the source from the github.com git repo mirror
> >> > * built Kudu's C++ components and tests in RELEASE configuration on
> >> CentOS
> >> > Linux release 7.9.2009 (Core) node
> >> > * run Kudu the tests using 'ctest -j2' command
> >> > * all tests pass except for a few scenarios involving Ranger and
> >> RangerKMS
> >> > in the following tests, but those seem to be test-only issues with the
> >> > mini_ranger_kms and mini_ranger wrappers (those scenarios pass in gerrit
> >> > pre-commit tests):
> >> > ** master_authz-itest
> >> > ** security-itest
> >> >
> >> > I also ran a smoke test running a small Kudu cluster and executing `kudu
> >> > perf loadgen`,
> >> > and it successfully completed.
> >> >
> >> >
> >> > Kind regards,
> >> >
> >> > Alexey
> >> >
> >> > On Wed, Aug 2, 2023 at 5:54 AM Yingchun Lai <laiyingc...@apache.org>
> >> > wrote:
> >> >
> >> > > Hello Kudu devs!
> >> > >
> >> > > The Apache Kudu team is happy to announce the first release candidate
> >> for
> >> > > Apache
> >> > > Kudu 1.17.0.
> >> > >
> >> > > Apache Kudu 1.17.0 is a minor release that offers many improvements and
> >> > > fixes
> >> > > since Apache Kudu 1.16.0.
> >> > >
> >> > > This is a source-only release. The artifacts have been staged here:
> >> > > https://dist.apache.org/repos/dist/dev/kudu/1.17.0-RC1
> >> > >
> >> > > Java convenience binaries in the form of a Maven repository are staged
> >> > > here:
> >> > > https://repository.apache.org/content/repositories/orgapachekudu-1104
> >> > >
> >> > > Linux (built on CentOS 7) and macOS (built on Ventura) test-only Kudu
> >> > > binary
> >> > > JAR artifacts are staged here:
> >> > > https://repository.apache.org/content/repositories/orgapachekudu-1105
> >> > > https://repository.apache.org/content/repositories/orgapachekudu-1106
> >> > >
> >> > > It is tagged in Git as 1.17.0-RC1 and signed with my key (found in the
> >> > > KEYS file
> >> > > below). Its commit hash is 34243b3d0777597862aa6d3b51fd401f72d8bbf2 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=34243b3d0777597862aa6d3b51fd401f72d8bbf2
> >> > > https://github.com/apache/kudu/releases/tag/1.17.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.17.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
> >> > > Aug 5th 23:00:00 UTC 2023.
> >> > >
> >> > > Thank You,
> >> > > Yingchun Lai
> >> > >
> >> > > [1] https://www.apache.org/foundation/voting.html#ReleaseVotes
> >> > >
> >> >
> >>

Reply via email to