+1 (non-binding) Built on CentOS 7.3 in release mode as well. I had one C++ test failure when I built this with Ninja due to it running "which ninja" and on this machine it's called ninja-build. I was able to work around it by adding a symlink called ninja to the $PATH, that way the actual tests passed too. As Ninja is experimental, this is not a problem.
mvn test verify in java/ succeeded without failures though. > On 2018. May 9., at 17:30, Andrew Wong <[email protected]> wrote: > > +1 > > I built on CentOS 7.3 and ran all C++ tests in release mode and with TSAN. > All passed. > > On Wed, May 9, 2018 at 12:08 AM, Mike Percy <[email protected]> wrote: > >> I hit that issue too, but running >> >> unset GLOG_colorlogtostderr >> >> Made those tests pass for me as well. >> >> Mike >> >> Sent from my iPhone >> >>> On May 8, 2018, at 11:40 PM, Alexey Serbin <[email protected]> wrote: >>> >>> +1 >>> >>> I built 1.7.1 RC1 (release) on CentOS 6.6. >>> >>> All C++ tests passed except for the following ones: >>> >>> ToolTest.TestTopLevelHelp >>> ToolTest.TestModeHelp >>> ToolTest.TestActionHelp >>> ToolTest.TestActionMissingRequiredArg >>> >>> However, I don't think it's an issue that should block the release (I >> hope to have some time to a look at the breakages soon). >>> >>> Thank you very much for taking care of the release management for 1.7.1, >> Grant! >>> >>> >>> >>> Kind regards, >>> >>> Alexey >>> >>> >>> >>>> On 5/8/18 2:06 PM, Hao Hao wrote: >>>> +1 >>>> >>>> * Release note looks good >>>> * Built in Debug/release mode on el7, all tests passed. >>>> >>>> Best, >>>> Hao >>>> >>>>> On Tue, May 8, 2018 at 8:59 AM, Mike Percy <[email protected]> wrote: >>>>> >>>>> +1 >>>>> >>>>> * Release notes look good >>>>> * Tag matches archive >>>>> * LICENSE file looks fine >>>>> * Built in release mode on Ubuntu 16.04, all tests passed >>>>> >>>>> Thanks for managing the release, Grant! >>>>> >>>>> Mike >>>>> >>>>>> On Wed, May 2, 2018 at 2:44 PM, Grant Henke <[email protected]> >> wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> The Apache Kudu team is happy to announce the first release candidate >> for >>>>>> Apache Kudu 1.7.1. >>>>>> >>>>>> Apache Kudu 1.7.1 is a bug-fix release which fixes critical issues in >>>>> Kudu >>>>>> 1.7.0. >>>>>> >>>>>> The is a source-only release. The artifacts have been staged here: >>>>>> https://dist.apache.org/repos/dist/dev/kudu/1.7.1-RC1/ >>>>>> >>>>>> Java convenience binaries in the form of a Maven repository are staged >>>>>> here: >>>>>> https://repository.apache.org/content/repositories/ >> orgapachekudu-1020/ >>>>>> >>>>>> It is tagged in Git as 1.7.1-RC1 and the corresponding git hash is the >>>>>> following: >>>>>> *https://git-wip-us.apache.org/repos/asf?p=kudu.git;a=commit >>>>>> ;h=ffc01ab7238eb08914deccc38beda82e1ec862b5 >>>>>> <https://git-wip-us.apache.org/repos/asf?p=kudu.git;a=commit >>>>>> ;h=ffc01ab7238eb08914deccc38beda82e1ec862b5>* >>>>>> >>>>>> The release notes can be found here: >>>>>> https://github.com/apache/kudu/blob/1.7.1-RC1/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. >>>>>> >>>>>> The vote will run until Friday, May 4th at 11PM PDT. >>>>>> >>>>>> Thank you, >>>>>> Grant >>>>>> >>>>>> -- >>>>>> Grant Henke >>>>>> Software Engineer | Cloudera >>>>>> [email protected] | twitter.com/gchenke | linkedin.com/in/granthenke >>>>>> >>> >> >>
signature.asc
Description: Message signed with OpenPGP
