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 <[email protected]>
Date: 2016-07-03T14:08:17Z
[FLINK-4145] [core] Configure port range for JMXReporterTest
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
