[
https://issues.apache.org/jira/browse/FLUME-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16221370#comment-16221370
]
ASF subversion and git services commented on FLUME-199:
-------------------------------------------------------
Commit e4312ad1acfd28e23405e6775374948fa35d5e40 in flume's branch
refs/heads/trunk from [~andrasbeni]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=e4312ad ]
FLUME-199. Remove hardcoded ports from unit tests
Many unit tests use hardcoded port numbers which leads to flakiness and causes
problems when running builds in parallel.
This patch fixes this issue by searching for available ports instead of the
hardcoded ones.
This closes #124
Reviewers: Miklos Csanady, Ferenc Szabo
(Andras Beni via Denes Arvay)
> 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
>
> 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)
