Done, disabled except pre-commit + hadoop-1.
Thanks
Szehon
On Thu, Mar 20, 2014 at 7:34 PM, Ashutosh Chauhan wrote:
> Szehon,
> Can you disable other builds? Seems like we didnt make much progress even
> today.
>
> Thanks,
> Ashutosh
>
>
> On Thu, Mar 20, 2014 at 10:54 AM, Szehon Ho wrote:
>
>
Szehon,
Can you disable other builds? Seems like we didnt make much progress even
today.
Thanks,
Ashutosh
On Thu, Mar 20, 2014 at 10:54 AM, Szehon Ho wrote:
> Yea it definitely makes sense. That is removing coverage of hadoop-2 and
> 0.13, but these can be run on demand or on less frequent sc
Yea it definitely makes sense. That is removing coverage of hadoop-2 and
0.13, but these can be run on demand or on less frequent schedule like
weekly. Maybe Harish has comment for 0.13 branch builds.
Thanks
Szehon
On Thu, Mar 20, 2014 at 10:37 AM, Ashutosh Chauhan wrote:
> Just to be clear,
Just to be clear, only run pre-commit builds (which runs patch on trunk on
hadoop-1). Thoughts?
On Thu, Mar 20, 2014 at 10:32 AM, Ashutosh Chauhan wrote:
> I wonder shall we disable all Hive builds except for trunk on hadoop-1 to
> expedite the queue. Since, thats the primary combination we are
I wonder shall we disable all Hive builds except for trunk on hadoop-1 to
expedite the queue. Since, thats the primary combination we are using to
inform committing patches, that will help to move queue faster. Without
patches getting committed (since queue is not moving fast enough) other
builds a
Hi,
Thanks for keeping an eye. There's another point worth mentioning, that a
confusing, others had also reported about the same situation. The
pre-commit test run can seem to take long because its waiting for the the
PTest server to finish the other hive builds (trunk/0.13), which I believed
ha
Okay. That could well be. However, test hanging seemingly happened before.
The queue just gets longer when it does happen.
Thanks,
Xuefu
On Wed, Mar 19, 2014 at 3:40 PM, Ashutosh Chauhan wrote:
> It seems like issue is getting in spot instances. Doesn't seem like
> anything specific to patch or
It seems like issue is getting in spot instances. Doesn't seem like
anything specific to patch or test framework. I dont think we have much
choice there rather than let tests to take whatever time they take. So,
killing a test run won't help much, I guess.
Thanks,
Ashutosh
On Wed, Mar 19, 2014 a
I had to kill the following, which had been running for more than 7 hours.
Let's see if the problem remains.
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1872/
--Xuefu
