I get a directory listing when I click through. 

Build status on Apache Jenkins looks pretty good - 
https://builds.apache.org/job/HBase-0.98/ - and I don't have failing tests on 
my local dev boxes. Any chance you can help us track down what's different 
about your environment? 


> On Aug 31, 2014, at 3:36 PM, Jean-Marc Spaggiari <jean-m...@spaggiari.org> 
> wrote:
> 
> Here are the results.
> 
> 4 builds, 4 computers, 4 failed.
> 
> HTH
> 
> http://server.distparser.com:81/hbase/
> 
> Let me know if you want me to run anything else.
> 
> JM
> 
> 
> 2014-08-30 14:29 GMT-04:00 Ted Yu <yuzhih...@gmail.com>:
> 
>> Jean-Marc:
>> I couldn't reproduce the test failure - on Mac or Linux.
>> 
>> Can you apply the following and run test again ?
>> http://pastebin.com/Z1czdBes
>> 
>> It would reveal whether log replay didn't bring back the labels written
>> prior to RS restart, or the new labels were not written successfully.
>> 
>> Thanks
>> 
>> 
>> On Fri, Aug 29, 2014 at 6:08 PM, Jean-Marc Spaggiari <
>> jean-m...@spaggiari.org> wrote:
>> 
>>> I will see if I can build something where the logs are automatically
>>> uploaded so that will make easier to look at them.
>>> 
>>> I just pushed the files related to this test.
>> http://www.spaggiari.org/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay.txt
>> http://www.spaggiari.org/org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay-output.txt
>>> 
>>> HTH
>>> 
>>> JM
>>> 
>>> 
>>> 2014-08-29 20:05 GMT-04:00 Andrew Purtell <apurt...@apache.org>:
>>> 
>>>> On Fri, Aug 29, 2014 at 5:01 PM, Jean-Marc Spaggiari <
>>>> jean-m...@spaggiari.org> wrote:
>>>> 
>>>>> Here are the logs for
>> testAddVisibilityLabelsOnRSRestart(org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDistributedLogReplay)
>>>>> : http://www.spaggiari.org/hbase-0.98.6.logs
>>>>> 
>>>>> Let me know if you need any other file. This is the standard output
>>> with
>>>>> -X.
>>>> 
>>>> I was looking for the
>>>> hbase-server/target/surefire-reports/<test-name>-output.txt file, but
>>> ​you
>>>> could run the test with -Dtest.output.tofile=false​ and capture
>> standard
>>>> output too.
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Best regards,
>>>> 
>>>>   - Andy
>>>> 
>>>> Problems worthy of attack prove their worth by hitting back. - Piet
>> Hein
>>>> (via Tom White)
>> 

Reply via email to