答复: 回复： [VOTE] Apache Kudu 1.10.0-RC2

[helifu <hz...@corp.netease.com>]

-1
* All C++ tests passed in slow mode on Debian8.9 (including debug/release)
except the below one:
  - sentry_authz_provider-test --gtest_filter=TestSentryClientMetrics.Basic:
sometimes it works, sometimes it doesn't;
    /mnt/ddb/2/helif/apache/kudu/src/kudu/master/sentry_authz_provider-test.
cc:1415: Failure
    Expected: (2000000) < (hist->histogram()->MaxValue()), actual: 2000000
vs 1998921
* All Java tests passed on Debian8.9 using gradlew;


何李夫
2019-06-27 20:46:19

-----邮件原件-----
发件人: dev-return-6279-hzhelifu=corp.netease.com@kudu.apache.org
<de...@kudu.apache.org> 代表 赖迎春
发送时间: 2019年6月27日 20:17
收件人: kudu-dev <de...@kudu.apache.org>
主题: 回复： [VOTE] Apache Kudu 1.10.0-RC2

+1. But I'll point out that build hung on my Ubuntu 18.04 in DEBUG type,
I open an issue https://issues.apache.org/jira/browse/KUDU-2879. It's an old
problem and seems happend on my own Ubuntu 18.04 environment.




------------------ 原始邮件 ------------------
发件人: "Grant Henke"<gh...@cloudera.com.INVALID>;
发送时间: 2019年6月27日(星期四) 凌晨2:26
收件人: "kudu-dev"<de...@kudu.apache.org>;

主题: Re: [VOTE] Apache Kudu 1.10.0-RC2



I agree, it's a small issue but likely worth resolving. I will cut a new RC
asap.

On Wed, Jun 26, 2019 at 11:14 AM Andrew Wong <aw...@cloudera.com.invalid>
wrote:

> +1 but I'll point out that I had trouble initially building on CentOS 
> +6 and
> CentOS 7, and got around it by applying the following patch:
> https://gerrit.cloudera.org/c/13732/
>
> Since this is a source-only release, we may want to cut another 
> release candidate.
>
> I tested on CentOS 6 in release mode and all tests passed.
>
>
> On Tue, Jun 25, 2019 at 10:15 AM Todd Lipcon 
> <to...@cloudera.com.invalid>
> wrote:
>
> > +1. I built this tarball on el7 using various compilers (clang 6, 
> > +clang
> 8,
> > devtoolset-3, devtoolset-4, devtoolset-6, and devtoolset-7). I hit 
> > an internal compiler error on devtoolset-7 but I don't think that's 
> > really critical (clearly a gcc bug).
> >
> > I ran YCSB for a couple billion rows with various workloads against 
> > a single node, performance looked pretty good.
> >
> > -Todd
> >
> > On Fri, Jun 21, 2019 at 7:35 PM Grant Henke 
> > <ghenke@cloudera.com.invalid
> >
> > wrote:
> >
> > > Hello Kudu devs!
> > >
> > > The Apache Kudu team is happy to announce the second release 
> > > candidate
> > for
> > > Apache Kudu 1.10.0.
> > >
> > > Apache Kudu 1.10.0 is a minor release that offers many 
> > > improvements and fixes since the prior release.
> > >
> > > This is a source-only release. The artifacts have been staged here:
> > > https://dist.apache.org/repos/dist/dev/kudu/1.10.0-RC2/
> > >
> > > Java convenience binaries in the form of a Maven repository are 
> > > staged
> > > here:
> > > https://repository.apache.org/content/repositories/orgapachekudu-1
> > > 036/
> > >
> > > It is tagged in Git as 1.10.0-RC2 and the corresponding hash is 
> > > the
> > > following:
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=428d175bd954
> f50aed7a5c23e818630a3b557742
> > >
> > > The release notes can be found here:
> > >
> >
> https://github.com/apache/kudu/blob/branch-1.10.x/docs/release_notes.a
> doc
> > >
> > > 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 Tuesday, June 25th at 11:59AM PST. This is 
> > > a
> bit
> > > over the suggested 72 hours due to the weekend.
> > >
> > > Thank you,
> > > Grant
> > >
> > > --
> > > Grant Henke
> > > Software Engineer | Cloudera
> > > grant@cloudera.com | twitter.com/gchenke | 
> > > linkedin.com/in/granthenke
> > >
> >
> >
> > --
> > Todd Lipcon
> > Software Engineer, Cloudera
> >
>
>
> --
> Andrew Wong
>


--
Grant Henke
Software Engineer | Cloudera
grant@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke