I had two clean full builds/unit test on my internal setup and the latest
build went back to ~4325 total tests and failures on Procedure relate tests
cases.

I don't think mob is responsible for these failures.

Jon.

On Wed, Jul 22, 2015 at 4:32 PM, Jonathan Hsieh <j...@cloudera.com> wrote:

> Although the the precommit buiid passed, and the compilation and mob
> testing I ran after before the merge was commited passed, It looks like
> the first full build after the merge [1] failed.  It looked like
> something hung along the way, and that most of the previous builds had
> failed for various reasons. :(
>
> I kicked it off again have it do another try.  If it is mob related we'll
> take hunt it down and take care of it.
>
> Jon.
>
> [1] https://builds.apache.org/job/HBase-TRUNK/6672/
>
> On Wed, Jul 22, 2015 at 1:16 PM, Jonathan Hsieh <j...@cloudera.com> wrote:
>
>> I've merged the code in to master.  Thanks for all the hard work
>> Jingcheng and thanks to all who have been involved with reviews,
>> discussion, and voting!
>>
>> Jon
>>
>> On Wed, Jul 22, 2015 at 12:45 AM, Jingcheng Du <jingcheng...@intel.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> The vote passes with 8 +1s and no -1. Thanks all for guiding, helping and
>>> voting!
>>> We will work on the merge activities and will let guys know about the
>>> detailed plan for merge time.
>>> And thanks Jon for helping merge this branch to trunk!
>>>
>>> Regards,
>>> Jingcheng
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://apache-hbase.679495.n3.nabble.com/RESULT-VOTE-Merge-branch-hbase-11339-HBase-MOB-to-trunk-tp4073446.html
>>> Sent from the HBase Developer mailing list archive at Nabble.com.
>>>
>>
>>
>>
>> --
>> // Jonathan Hsieh (shay)
>> // HBase Tech Lead, Software Engineer, Cloudera
>> // j...@cloudera.com // @jmhsieh
>>
>>
>
>
>
> --
> // Jonathan Hsieh (shay)
> // HBase Tech Lead, Software Engineer, Cloudera
> // j...@cloudera.com // @jmhsieh
>
>



-- 
// Jonathan Hsieh (shay)
// HBase Tech Lead, Software Engineer, Cloudera
// j...@cloudera.com // @jmhsieh

Reply via email to