+1 I built the C++ and Java code out of the 1.11.1-RC2 tag on CentOS6.6 x86_64 in RELEASE mode, ran C++ tests using dist-test and Java tests using './gradlew test'.
On Tue, Nov 19, 2019 at 3:17 PM Hao Hao <[email protected]> wrote: > +1 built at DEBUG mode and ran on CentOS 7.3, all the c++ and java tests > passed. > > On Tue, Nov 19, 2019 at 2:26 PM Andrew Wong <[email protected]> > wrote: > > > +1 > > > > - I built in RELEASE mode on Centos 7.3 > > - Looked at the updated release notes > > - Looked through the source release for references to libnuma, and didn't > > see anything unexpected > > > > > > On Mon, Nov 18, 2019 at 1:47 AM Adar Lieber-Dembo > > <[email protected]> > > wrote: > > > > > +1 > > > > > > I ran DEBUG tests in slow mode on Ubuntu 18.04 and CentOS 6.6. All > > passed. > > > > > > On Sat, Nov 16, 2019 at 1:36 PM Attila Bukor <[email protected]> > wrote: > > > > > > > > +1 > > > > > > > > - Verified checksum, the signature and that the archive was created > > from > > > the tag > > > > - Successfully built Kudu in release mode on CentOS 7.3 and macOS > > Mojave > > > 10.14.6 > > > > - Ran Java and C++ tests in slow mode on CentOS 7.3, only one failure > > in > > > each, > > > > both environmental (address already in use, too many open files) > > > > - Ran Java tests on macOS Mojave with one failure (lsof missing). > > > > - Successfully built Java and Spark examples using the staged JARs on > > > CentOS and > > > > the Java examples also on macOS. Spark examples build failed on > > macOS, > > > but it > > > > seems it's not specific to this version. Opened a JIRA: KUDU-2997 > > > > - Read the release notes > > > > > > > > Attila > > > > > > > > On Fri, Nov 15, 2019 at 08:41:35PM -0800, Alexey Serbin wrote: > > > > > Hello Kudu devs! > > > > > > > > > > The Apache Kudu team is happy to announce the third release > candidate > > > (RC3) > > > > > for Apache Kudu 1.10.1. > > > > > > > > > > Apache Kudu 1.10.1 is a bug-fix release which fixes one critical > > > licensing > > > > > and few other issues in Kudu 1.10.0. > > > > > > > > > > This is a source-only release. The artifacts have been staged here: > > > > > https://dist.apache.org/repos/dist/dev/kudu/1.10.1-RC3/ > > > > > > > > > > Java convenience binaries in the form of a Maven repository are > > staged > > > here: > > > > > > > > https://repository.apache.org/content/repositories/orgapachekudu-1053 > > > > > > > > > > Linux and macOS kudu-binary JAR artifacts are staged here > > > correspondingly: > > > > > > > > https://repository.apache.org/content/repositories/orgapachekudu-1054 > > > > > > > > https://repository.apache.org/content/repositories/orgapachekudu-1055 > > > > > > > > > > It is tagged in Git as 1.10.1-RC3 and the corresponding hash is the > > > > > following: > > > > > > > > > > > > > > > > https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=d7e2e998cf963dc98c568f264cc09c7c320cae0a > > > > > > > > > > The release notes can be found here: > > > > > > > > > > > https://github.com/apache/kudu/blob/branch-1.10.x/docs/release_notes.adoc > > > > > > > > > > The KEYS file to verify the artifact signatures can be found here: > > > > > https://dist.apache.org/repos/dist/release/kudu/KEYS > > > > > > > > > > I'd suggest going through the README and 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://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=8a6faaa93f3e206ac75e8087731daccaf7ab646a > > > > > > > > > > This vote runs until Tue Nov 19 15:00:00 PST 2019. > > > > > That's over 72 hours from the time of sending out this e-mail > message > > > due > > > > > to the weekend. > > > > > > > > > > > > > > > Kind regads, > > > > > > > > > > Alexey > > > > > > > > > -- > > Andrew Wong > > >
