You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/03 14:21:10 UTC
[jira] [Commented] (FLINK-4145) JmxReporterTest fails due to port
conflicts
[ https://issues.apache.org/jira/browse/FLINK-4145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360554#comment-15360554 ]
ASF GitHub Bot commented on FLINK-4145:
---------------------------------------
GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/2193
[FLINK-4145] [core] Configure port range for JMXReporterTest
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.
Can you review this, @zentol?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/uce/flink 4145-jmx_test
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2193.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2193
----
commit dbe217a1bd9eaa9a98c7ae9800fec8d2af26e2f3
Author: Ufuk Celebi <uc...@apache.org>
Date: 2016-07-03T14:08:17Z
[FLINK-4145] [core] Configure port range for JMXReporterTest
----
> 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
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
> 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)