hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: failed unit test due to locked directory
Date Mon, 08 Aug 2011 22:55:55 GMT
I added it. Should trigger on next trunk build.
St.Ack

On Mon, Aug 8, 2011 at 3:41 PM, Ted Yu <yuzhihong@gmail.com> wrote:
> How about something like the following:
>
> $ ps aux | grep `jps | grep surefirebooter | awk '{print $1}'` | grep -i
> 'hbase' | grep 'target/surefire'
> hadoop    9259 34.6  1.8 2087596 594672 pts/0  Sl+  22:38   0:27
> /usr/java/jdk1.6.0_23/jre/bin/java -enableassertions -Xmx1400m -jar
> /home/hadoop/hbase/target/surefire/surefirebooter4503367661299017984.jar
> /home/hadoop/hbase/target/surefire/surefire574928600779662143tmp
> /home/hadoop/hbase/target/surefire/surefire5612437413429415234tmp
>
> We still need to distinguish the tests between 0.90 and TRUNK builds.
>
> Getting jstack on top of the above would be useful.
>
> On Mon, Aug 8, 2011 at 3:30 PM, Stack <stack@duboce.net> wrote:
>
>> On Mon, Aug 8, 2011 at 3:20 PM, Ted Yu <yuzhihong@gmail.com> wrote:
>> > BTW how can we know whether there were hanging surefire processes on
>> Jenkins
>> > ?
>> >
>>
>> We can run a few shell commands before the build starts (I recently
>> added printing out what the ulimit on the machine is).  Should we add
>> listing of java processes (There's probably loads running on the box;
>> would need to figure which were ours)?
>>
>> St.Ack
>>
>

Mime
View raw message