flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ufuk Celebi (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLINK-4145) JmxReporterTest fails due to port conflicts
Date Sun, 03 Jul 2016 14:08:10 GMT
Ufuk Celebi created FLINK-4145:

             Summary: 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
             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

View raw message