hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14378) Get TestAccessController* passing again on branch-1
Date Thu, 24 Sep 2015 20:44:05 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906973#comment-14906973
] 

stack commented on HBASE-14378:
-------------------------------

kalashnikov:hbase.git.commit stack$ python ./dev-support/findHangingTests.py https://builds.apache.org/job/PreCommit-HBASE-Build/15723//consoleText
Fetching the console output from the URL
Printing hanging tests
Hanging test : org.apache.hadoop.hbase.client.TestFastFail
Printing Failing tests
Failing test : org.apache.hadoop.hbase.master.TestDistributedLogSplitting


TestDistributedLogSplitting fails locally too. Reverting the change to this test from this
patch has it passing again.

The disabling done over in HBASE-14421 is not enough for TestFastFail. It starts this test
client.TestFastFail#testFastFail , and never finishes. Am going to comment it out in a different
issue.

> Get TestAccessController* passing again on branch-1
> ---------------------------------------------------
>
>                 Key: HBASE-14378
>                 URL: https://issues.apache.org/jira/browse/HBASE-14378
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: stack
>            Assignee: stack
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>
>         Attachments: 14378.branch-1.txt, 14378.branch-1.v2.txt, 14378.branch-1.v2.txt,
14378.branch-1.v2.txt, 14378.branch-1.v6.txt, 14386.branch-1.v3 (1).txt, 14386.branch-1.v3.txt,
14386.branch-1.v3.txt, 14386.branch-1.v4.do.nothing.txt, 14386.branch-1.v5.txt
>
>
> TestAccessController* are failing reliably on branch-1. They go zombie. I learned that
setting the junit test timeout facility on the class doesn't make the zombie timeout nor does
setting a timeout on each test turn zombies to test failures; the test goes zombie on the
way out in the tear down of the cluster.
> Digging, we are out of handlers... all are occupied.
> 3dacee6 HBASE-14290 Spin up less threads in tests cut the default thread count to 3 from
10. Putting the value back on these tests seems to make them pass reliably when I run locally.
 For good measure, I'll add in the timeouts .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message