hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Coleman" <>
Subject RE: setting up a branch for testing
Date Tue, 03 Mar 2015 00:52:03 GMT
I have one "not being used" Dell PE R900 32 gigs of ram 800 gigs of HDD
space with 2 hot swaps and win server 2008 and a spare static ip.


-----Original Message-----
From: Sergey Shelukhin [] 
Sent: Monday, March 02, 2015 4:59 PM
Subject: Re: setting up a branch for testing

Ping; can you post the slides?
From: Brock Noland <>
Sent: Thursday, February 19, 2015 5:08 PM
Subject: Re: setting up a branch for testing

I will actually be talking about this tonight at the Hive meetup. I will
post slides here afterwards.

On Thu, Feb 19, 2015 at 2:28 PM, Sergey Shelukhin <>
> Can you elaborate on how many machines are needed, minimum (is it 1+, just
determined by the throughput of QA runs that we want; or is there some fixed
requirement too), and what is the setup/process to make them work with
HiveQA (in general so we'd know how we can provide machines)?
> Thanks!
> ________________________________________
> From: Szehon <>
> Sent: Friday, January 23, 2015 7:38 PM
> To:
> Subject: Re: setting up a branch for testing
> Yea but for precommit testing it would need a cluster setup that runs an
instance of Ptest server.  We only have spark branch setup for that other
than trunk, we have one cluster running spark and another running trunk.
> Setup is doable (actually just need to setup master) but takes some steps,
and physical machines.
> Thanks
> Szehon
>> On Jan 23, 2015, at 6:04 PM, Sergey Shelukhin <>
>> Hi.
>> Hive dev doc mentions that patches can be tested by HiveQA against 
>> the branch by supplying the branch name in the patch name.
>> However, as far as I understand this requires some setup for each 
>> specific branch.
>> Is it possible to set up "llap" branch for HiveQA testing?
>> --
>> NOTICE: This message is intended for the use of the individual or 
>> entity to which it is addressed and may contain information that is 
>> confidential, privileged and exempt from disclosure under applicable 
>> law. If the reader of this message is not the intended recipient, you 
>> are hereby notified that any printing, copying, dissemination, 
>> distribution, disclosure or forwarding of this communication is 
>> strictly prohibited. If you have received this communication in 
>> error, please contact the sender immediately and delete it from your
system. Thank You.

View raw message