Created HIVE-13402 to disable the tests. Have narrowed it down to 3 hanging
tests. From what I understand the TestVectorTimestampExpressions tests have
already been fixed.
On Tue, Mar 29, 2016 at 10:27 AM, Ashutosh Chauhan
wrote:
> I agree with disabling these tests till we are able to fix it. S
I agree with disabling these tests till we are able to fix it. Since bug
seems to be in spark runtime, it may take a little while to fix it.
Increased run time for QA till then would be waste of resources.
Thanks,
Ashutosh
On Tue, Mar 29, 2016 at 9:06 AM, Siddharth Seth wrote:
> Thanks Szehon.
Thanks Szehon. Should we disable the tests while the issue is resolved.
There's a backlog of 17 patches - which will take over 2 days to run at
this point.
Also, HIVE-13365 ended up running for over 8 hours yesterday. Maybe we
should put a cap on max runtime for a single run. Anyone know how to do
Yea we looked at it before.. its tracked by HIVE-13223, caused by
HIVE-13040.
Because it hangs these tests take 2 hours max now before they are killed,
hence each run taking over 3 hours.
Ashutosh is looking I believe, I havent had a chance to take a look myself.
Szehon
On Mon, Mar 28, 2016 at
There's several tests which are failing consistently. Should we disable
these and create blocker jiras to fix and enable thees for the next
release. The list of test is at the end of the mail.
Also, each pre-commit run seems to be taking over 3 hours. Is this normal ?
Having test results come back
