zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2922) Flaky Test: org.apache.zookeeper.test.LoadFromLogTest
Date Fri, 20 Oct 2017 19:51:00 GMT

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

ASF GitHub Bot commented on ZOOKEEPER-2922:
-------------------------------------------

Github user afine commented on the issue:

    https://github.com/apache/zookeeper/pull/402
  
    I think there is a better way to do this. Picking a new port for each test seems to be
a workaround for failing to clean up the resources utilized by a failing test. It would be
better if we cleaned up properly after a test execution. 
    
    Since this is the method we used to fix the test in another branch I think it is up to
the discretion of the committers, but it would be nice to not leak any resources from our
tests.


> Flaky Test: org.apache.zookeeper.test.LoadFromLogTest
> -----------------------------------------------------
>
>                 Key: ZOOKEEPER-2922
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2922
>             Project: ZooKeeper
>          Issue Type: Test
>          Components: server, tests
>            Reporter: Andor Molnar
>            Assignee: Andor Molnar
>              Labels: flaky, flaky-test
>             Fix For: 3.4.12
>
>
> Backport changes of flaky test fix to branch-3.4 :
> https://issues.apache.org/jira/browse/ZOOKEEPER-2484
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message