You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Denes Arvay (JIRA)" <ji...@apache.org> on 2017/10/26 22:39:00 UTC

[jira] [Resolved] (FLUME-199) Unit tests should hunt for available ports if defaults are in use

     [ https://issues.apache.org/jira/browse/FLUME-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denes Arvay resolved FLUME-199.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

Thank you [~andrasbeni] for the patch, [~mcsanady] and [~fszabo] for the reviews, I have pushed this to trunk.

> Unit tests should hunt for available ports if defaults are in use
> -----------------------------------------------------------------
>
>                 Key: FLUME-199
>                 URL: https://issues.apache.org/jira/browse/FLUME-199
>             Project: Flume
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 1.5.0.1
>            Reporter: E. Sammer
>            Assignee: Santiago M. Mola
>            Priority: Minor
>             Fix For: 1.9.0
>
>
> Currently, some of the unit tests fail if flume is running while tests are running. This leads to false positives in failure detection and slows down the dev cycle as one has to remember not to run flume while tests are in progress. It would be an improvement to "hunt" for an open port if the default port(s) are already in use during testing.



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