[jira] [Updated] (FLINK-8161) Flakey YARNSessionCapacitySchedulerITCase on Travis
[
https://issues.apache.org/jira/browse/FLINK-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann updated FLINK-8161:
-
Fix Version/s: (was: 1.5.0)
1.5.1
> Flakey YARNSessionCapacitySchedulerITCase on Travis
> ---
>
> Key: FLINK-8161
> URL: https://issues.apache.org/jira/browse/FLINK-8161
> Project: Flink
> Issue Type: Bug
> Components: Tests, YARN
>Affects Versions: 1.5.0
>Reporter: Till Rohrmann
>Assignee: Till Rohrmann
>Priority: Critical
> Labels: test-stability
> Fix For: 1.5.1
>
> Attachments: 24547.10.tar.gz,
> api.travis-ci.org_v3_job_380488917_log.tar.xz
>
>
> The {{YARNSessionCapacitySchedulerITCase}} spuriously fails on Travis because
> it now contains {{2017-11-25 22:49:49,204 WARN
> akka.remote.transport.netty.NettyTransport- Remote
> connection to [null] failed with java.nio.channels.NotYetConnectedException}}
> from time to time in the logs. I suspect that this is due to switching from
> Flakka to Akka 2.4.0. In order to solve this problem I propose to add this
> log statement to the whitelisted log statements.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLINK-8161) Flakey YARNSessionCapacitySchedulerITCase on Travis
[
https://issues.apache.org/jira/browse/FLINK-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Nuyanzin updated FLINK-8161:
---
Attachment: api.travis-ci.org_v3_job_380488917_log.tar.xz
> Flakey YARNSessionCapacitySchedulerITCase on Travis
> ---
>
> Key: FLINK-8161
> URL: https://issues.apache.org/jira/browse/FLINK-8161
> Project: Flink
> Issue Type: Bug
> Components: Tests, YARN
>Affects Versions: 1.5.0
>Reporter: Till Rohrmann
>Assignee: Till Rohrmann
>Priority: Critical
> Labels: test-stability
> Fix For: 1.5.0
>
> Attachments: 24547.10.tar.gz,
> api.travis-ci.org_v3_job_380488917_log.tar.xz
>
>
> The {{YARNSessionCapacitySchedulerITCase}} spuriously fails on Travis because
> it now contains {{2017-11-25 22:49:49,204 WARN
> akka.remote.transport.netty.NettyTransport- Remote
> connection to [null] failed with java.nio.channels.NotYetConnectedException}}
> from time to time in the logs. I suspect that this is due to switching from
> Flakka to Akka 2.4.0. In order to solve this problem I propose to add this
> log statement to the whitelisted log statements.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLINK-8161) Flakey YARNSessionCapacitySchedulerITCase on Travis
[
https://issues.apache.org/jira/browse/FLINK-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Nuyanzin updated FLINK-8161:
---
Attachment: 24547.10.tar.gz
> Flakey YARNSessionCapacitySchedulerITCase on Travis
> ---
>
> Key: FLINK-8161
> URL: https://issues.apache.org/jira/browse/FLINK-8161
> Project: Flink
> Issue Type: Bug
> Components: Tests, YARN
>Affects Versions: 1.5.0
>Reporter: Till Rohrmann
>Assignee: Till Rohrmann
>Priority: Critical
> Labels: test-stability
> Fix For: 1.5.0
>
> Attachments: 24547.10.tar.gz,
> api.travis-ci.org_v3_job_380488917_log.tar.xz
>
>
> The {{YARNSessionCapacitySchedulerITCase}} spuriously fails on Travis because
> it now contains {{2017-11-25 22:49:49,204 WARN
> akka.remote.transport.netty.NettyTransport- Remote
> connection to [null] failed with java.nio.channels.NotYetConnectedException}}
> from time to time in the logs. I suspect that this is due to switching from
> Flakka to Akka 2.4.0. In order to solve this problem I propose to add this
> log statement to the whitelisted log statements.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
