Re: accidental push to master

Thanks. https://gerrit.cloudera.org/#/c/9845/ On Wed, Mar 28, 2018 at 3:49 PM, Philip Zeyliger wrote: > If I had to guess, https://jenkins.impala.io/job/cherrypick-2.x-and-test/ > will skip the revert, because it doesn't have a Change-Id. Since it hasn't > happened, you can

Re: accidental push to master

If I had to guess, https://jenkins.impala.io/job/cherrypick-2.x-and-test/ will skip the revert, because it doesn't have a Change-Id. Since it hasn't happened, you can add 25218487533f6bf6959c32ff4ee38b77e0ab30b5 to the ignored commits list of 2.x (in branch 2.x) right now, and both commits will

accidental push to master

Hi, I accidentally pushed to refs/heads/master, and then immediately reverted, though also to refs/heads. This means there is a commit out there without a Change-Id again. What's the proper thing here to do for 2.x? Thanks, and sorry about that. commit 2c0926e2de22ecafafc460f2b31ca2423b8f7e98

Re: Re: Re: ORC scanner - points for discussion

It looks like the review is converging, so hopefully we can get this in soon and people can play around with it in their development environments some more. Also, I wanted to call out all of the bugs that Quanlong has found and been fixing in the ORC C++ library - he's found a whole bunch of

Re: FE build failure

Hi Philip, Thanks a lot for the detailed analysis. Michael On Wed, Mar 28, 2018 at 9:58 AM, Philip Zeyliger wrote: > Hi Michael, > > What's going on is that we're re-using build machines. I compared >

Re: FE build failure

https://gerrit.cloudera.org/#/c/9841/ is the review to remove "-noclean" from bootstrap_development, which I think will prevent this. -- Philip On Wed, Mar 28, 2018 at 9:58 AM, Philip Zeyliger wrote: > Hi Michael, > > What's going on is that we're re-using build machines.

Maintenance for jenkins.impala.io tonight

Hi all, We need to upgrade the plugin to address a security advisory released on Monday. Planning to restart jenkins around 8pm tonight. Please let me know if you want this to be deferred. -- Thanks, Michael

Re: FE build failure

Hi Michael, What's going on is that we're re-using build machines. I compared https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/1748/consoleFull and https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/1749/consoleFull. They're buliding the same thing, and 1749 is a lot farther along,

Re: FE build failure

https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/1748/ On Wed, Mar 28, 2018 at 9:34 AM, Philip Zeyliger wrote: > I see. That's surprising. Could you send me a URL to take a look? > > Thanks! > > -- Philip > > On Wed, Mar 28, 2018 at 9:30 AM, Michael Ho

Re: FE build failure

I see. That's surprising. Could you send me a URL to take a look? Thanks! -- Philip On Wed, Mar 28, 2018 at 9:30 AM, Michael Ho wrote: > Thanks Philip. This is GVO not my local dev machine. It's presumably > building from scratch. Could it be left over from some previous

Re: FE build failure

Thanks Philip. This is GVO not my local dev machine. It's presumably building from scratch. Could it be left over from some previous GVO ? On Wed, Mar 28, 2018 at 9:05 AM, Philip Zeyliger wrote: > Hi Michael, > > Most likely this is on account of switching to Hadoop 3 by

Re: FE build failure

Hi Michael, Most likely this is on account of switching to Hadoop 3 by default ( https://github.com/apache/impala/commit/0812f8737a4301e5b52cad9dc911589f9e98ecdb). I sent an e-mail out about this yesterday, but I think what you're seeing is a need to re-run buildall, and to possibly clean

FE build failure

During GVO, I ran into the following warning message (*maven.jenkins.cloudera.com : Name or service not known*) and eventually hit a compilation failure eventually. Not sure if anyone has run into this failure or if the warning message is a concern: [WARNING]