Re: [VOTE] 2.10.0 release candidate 2 (RC2)

Thanks to everyone who voted here. The voting window is now closed. I've sent out a separate results thread. On Tue, Sep 5, 2017 at 12:30 PM, Michael Brown wrote: > +1 (binding) > > - downloaded and verified tarballs > - compiled and ran core tests > - connected and ran a

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

+1 (binding) - downloaded and verified tarballs - compiled and ran core tests - connected and ran a few queries On Wed, Aug 30, 2017 at 11:35 PM, Bharath Vissapragada < bhara...@cloudera.com> wrote: > This is a vote to release Impala 2.10.0. > > - The artefacts for testing can be downloaded

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

+1 (binding) for RC2 Thanks for looking into this, Jim and Bharath. I agree that the issues is likely environmental. There was no concrete evidence of an ASAN-related product bug, and ASAN exhaustive is known to be flaky: https://issues.apache.org/jira/browse/IMPALA-5218 I ran release tests of

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

Yeah, this jenkins.impala.io environment is pretty stable for DEBUG builds with core test exploration, but ASAN builds are infrequently done on it, so there might be a flaky test situation that is either Jenkins-related or test-related, which doesn't directly implicate the RC. I'm still OK with

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

Jim, thanks for testing the ASAN configuration. I tested it in my own environment (centos6) and it has passed. I'm suspecting that either something is flaky or probably related to the build environment. On Thu, Aug 31, 2017 at 11:23 PM, Jim Apple wrote: > I think ASAN

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

I think ASAN doesn't work with FE tests - I mistakenly left them in for this run. We have never before seen two jobs on the same worker in jenkins.impala.io. Here's an ASAN rerun that is failing other e2e tests: https://jenkins.impala.io/view/Utility/job/ubuntu-16.04-from-scratch/222/parameters/

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

Thanks for testing, Jim. I looked into your build but could not determine what happened. I found no ASAN output in the logs. It's interesting that this test also fails with a crash: ERROR at teardown of TestGrantRevoke.test_role_update[exec_option: {'batch_size': 0, 'num_nodes': 0,

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

This ASAN testing failed: https://jenkins.impala.io/view/Utility/job/ubuntu-16.04-from-scratch/218/consoleFull failed in query_test/test_udfs.py::TestUdfExecution::test_ir_functions[exec_option: {'disable_codegen_rows_threshold': 0, 'disable_codegen': False, 'exec_single_node_rows_threshold': 0,

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

BTW, this Jenkins job includes the log of what it tested, which follows the Release Guide, so you should be able to follow along OK. All committers should have access to run that job, too, if you don't trust my result. I am also testing exhaustive (not just core) tests at

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

Clarification: +1 (binding) As a reminder, binding votes in the PPMC vote are not binding in the IPMC vote unless the voter is also an IPMC member. Since I am not, this is a PPMC "+1 (binding)" only. On Thu, Aug 31, 2017 at 6:19 AM, Jim Apple wrote: > +1 > >

Re: [VOTE] 2.10.0 release candidate 2 (RC2)

+1 https://jenkins.impala.io/job/release-test/20/console This tested following https://cwiki.apache.org/confluence/display/IMPALA/How+to+load+and+run+Impala+tests and https://cwiki.apache.org/confluence/display/IMPALA/How+to+Release#HowtoRelease-HowtoVoteonaReleaseCandidate. On Wed, Aug 30,