Re: Analyzing output of Jenkins build Was: Jenkins build is back to normal : HBase-TRUNK #2304

Top showed only one java process. I'll try this again once I get back. On Sun, Oct 9, 2011 at 9:24 PM, Todd Lipcon wrote: > That jstack just looks like the trace of the maven process - there > should be another JVM which is actually running the tests. > > -Todd > > On Sat, Oct 8, 2011 at 10:14 AM

Re: Analyzing output of Jenkins build Was: Jenkins build is back to normal : HBase-TRUNK #2304

That jstack just looks like the trace of the maven process - there should be another JVM which is actually running the tests. -Todd On Sat, Oct 8, 2011 at 10:14 AM, Li Pi wrote: > I got the thing to fail on my vmware box. Heres the stack trace. > > Doesn't look like the cache itself is hanging.

Build failed in Jenkins: HBase-TRUNK #2312

See Changes: [stack] HBASE-4561 Update Maven documentation in book -- [...truncated 1676 lines...] Running org.apache.hadoop.hbase.mapreduce.TestTableSplit Tests run: 1, Failures: 0, Errors: 0, Skipp

Build failed in Jenkins: HBase-TRUNK-on-Hadoop-23 #53

See Changes: [stack] HBASE-4561 Update Maven documentation in book [ramkrishna] HBASE-4540 OpenedRegionHandler is not enforcing atomicity of the operation it is performing . Also fixes HBASE-4539 (ram) [stack] HBASE-4430 Disab

Re: Maven 2 vs. 3

On Sun, Oct 9, 2011 at 4:05 PM, Jesse Yates wrote: > Opened HBASE-4561 for doing the update in the book. > Thanks. > Is the book what we are considering the gold standard or should we also > update another source too? > Book is the place. St.Ack

Jenkins build is back to normal : HBase-TRUNK #2310

See

Jenkins build is back to normal : HBase-0.92 #54

See

Re: Maven 2 vs. 3

Opened HBASE-4561 for doing the update in the book. Is the book what we are considering the gold standard or should we also update another source too? -Jesse Yates On Sun, Oct 9, 2011 at 3:30 PM, Ted Dunning wrote: > It's ok. It confuses me, too. > > I keep wondering how I knew some of these

Re: Maven 2 vs. 3

It's ok. It confuses me, too. I keep wondering how I knew some of these things enough to have commented as well as the other Ted does. Then I notice that it was him. On Sun, Oct 9, 2011 at 3:21 PM, Doug Meil wrote: > > Oops... Sorry, the "Ted" in my message was aimed at Ted Yu. > > > > > On 10

Re: Maven 2 vs. 3

Oops. Wrong group. I don't know definitively about hbase. I was spouting off about Mahout and hadn't noticed that your message wasn't like the previous 3 I had answered. A few months ago, there definitely was a problem with hbase, but I have no idea whether that is resolved. Moving toward 3 as

Re: Maven 2 vs. 3

Oops... Sorry, the "Ted" in my message was aimed at Ted Yu. On 10/9/11 6:19 PM, "Doug Meil" wrote: > >Hey Ted, we were working on a ticket a few months ago and I was having >trouble because I was working with Maven 3 and you said it wasn't >supported (or didn't work well). > >If that's not t

Re: Maven 2 vs. 3

Hey Ted, we were working on a ticket a few months ago and I was having trouble because I was working with Maven 3 and you said it wasn't supported (or didn't work well). If that's not the case anymore I'll update the book. On 10/9/11 4:31 PM, "Ted Dunning" wrote: >The book is already slightl

Re: Maven 2 vs. 3

The book is already slightly out of date. Maven 3 is better and handles almost all maven 2 builds pretty seamlessly. I don't see a problem with moving forward rather than back. On Sun, Oct 9, 2011 at 1:03 PM, Jesse Yates wrote: > So the book says to use Maven 2, rather than Maven 3. Is it just

HBASE-1744

Hi, Since I am not very familiar with Thrift, I am requesting more review for patch v7 of HBASE-1744. Thanks