You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2018/09/13 19:16:00 UTC

[jira] [Commented] (RATIS-319) Increase TestRaftServerJmx's timeout

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

Josh Elser commented on RATIS-319:
----------------------------------

Admittedly, I've been having slow nameservice lookups since a recent OSX version which is probably to blame for this. But anyways, it causes a test failure for something that isn't Ratis' fault :)

> Increase TestRaftServerJmx's timeout
> ------------------------------------
>
>                 Key: RATIS-319
>                 URL: https://issues.apache.org/jira/browse/RATIS-319
>             Project: Ratis
>          Issue Type: Task
>          Components: test
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Trivial
>
> TestRaftServerJmx has a timeout of 10s which I frequently run into on my daily-use laptop.
> {code:java}
> [INFO] Running org.apache.ratis.server.impl.TestRaftServerJmx
> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.872 s - in org.apache.ratis.server.impl.TestRaftServerJmx{code}
> Typically, I see a failure in shutting down the cluster. Let's kick out this timeout a little more.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)