han
Jagadale/Austin/Contr/IBM@IBMUS, Nishidha
Panpaliya/Austin/Contr/IBM@IBMUS, Valencia
Serrao/Austin/Contr/IBM@IBMUS
Date: 08/11/2016 05:53 PM
Subject:Re: Fw: Issues with tests in Release-mode Impala build
Hi Tim/Michael,
I've noticed some strange beh
/Austin/Contr/IBM@IBMUS, Nishidha
Panpaliya/Austin/Contr/IBM@IBMUS
Date: 08/03/2016 08:46 PM
Subject:Re: Fw: Issues with tests in Release-mode Impala build
Hi Valencia,
I'm not sure exactly what's happening but I have a couple of ideas:
1. You may be running into some
IBM@IBMUS
Date: 08/03/2016 08:46 PM
Subject: Re: Fw: Issues with tests in Release-mode Impala build
Hi Valencia,
I'm not sure exactly what's happening but I have a couple of ideas:
1. You may be running into some known bugs in pytest that causes custom
cluster tests to
lencia Serrao/Austin/Contr/IBM@IBMUS, Manish
Patil/Austin/Contr/IBM@IBMUS, Sudarshan
Jagadale/Austin/Contr/IBM@IBMUS, Nishidha
Panpaliya/Austin/Contr/IBM@IBMUS
Date: 08/04/2016 05:11 AM
Subject: Re: Fw: Issues with tests in Release-mode Impala build
Hi Va
Hi Valencia,
Apologies for the multiple replies. I'm at a conference and hadn't had
time previously to look into your problem in detail.
It's OK that the tests you cited previously are being skipped, and I
think for your purposes you can ignore those 3 skips. That said, the
run shouldn't be
Valencia,
Also ensure you've incorporated the fix for
https://issues.cloudera.org/browse/IMPALA-3630 ("exhaustive custom cluster
tests never run") .
Thanks.
On Wed, Aug 3, 2016 at 8:15 AM, Tim Armstrong
wrote:
> Hi Valencia,
> I'm not sure exactly what's happening
Valencia,
Could you also share with us the exact command you used to which the
pasted output of your latest message corresponds?
Thanks.
On Tue, Aug 2, 2016 at 9:25 PM, Valencia Serrao wrote:
> Hi Tim,
>
> To trace the exploration strategy var at each step leading to the
>
Hi Valencia,
I'm not sure exactly what's happening but I have a couple of ideas:
1. You may be running into some known bugs in pytest that causes custom
cluster tests to be skipped: see
https://issues.cloudera.org/browse/IMPALA-3614 . We don't see that on
Impala master but maybe
Hi Tim,
To trace the exploration strategy var at each step leading to the
"test_spilling" test, I put a few print statements for it. I observed that,
once the process flow reaches the impala_test_suite.py the strategy is
changed to 'core'. The logs printed as follows: (logs marked pink)