You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2016/07/05 07:51:10 UTC
[jira] [Resolved] (FLINK-4145) JmxReporterTest fails due to port
conflicts
[ https://issues.apache.org/jira/browse/FLINK-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler resolved FLINK-4145.
-------------------------------------
Resolution: Fixed
Tests were hardened in 647b4c57781ed33467cd0946a34d63be737d66e8.
> JmxReporterTest fails due to port conflicts
> -------------------------------------------
>
> Key: FLINK-4145
> URL: https://issues.apache.org/jira/browse/FLINK-4145
> Project: Flink
> Issue Type: Bug
> Components: Local Runtime, Metrics
> Reporter: Ufuk Celebi
> Assignee: Chesnay Schepler
> Labels: test-stability
> Fix For: 1.1.0
>
>
> I saw multiple failures of the {{JmxReporterTest}} most likely due to a port conflicts. The test relies on the default JMX reporter port range, which spans 5 ports. Running on Travis with multiple concurrent builds and bad timings, this can lead to port conflicts.
> Some example failed runs:
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/141999066/log.txt (one out of 5 jobs failed)
> https://travis-ci.org/uce/flink/builds/141917901 (all 5 jobs failed)
> I propose to take the fork number into account (like the forkable Flink testing cluster) and configure a larger port range.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)