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 2017/11/27 16:42:00 UTC

[jira] [Commented] (FLINK-8161) Flakey YARNSessionCapacitySchedulerITCase on Travis

    [ https://issues.apache.org/jira/browse/FLINK-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267023#comment-16267023 ] 

ASF GitHub Bot commented on FLINK-8161:
---------------------------------------

GitHub user tillrohrmann opened a pull request:

    https://github.com/apache/flink/pull/5085

    [FLINK-8161] [tests] Harden YARNSessionCapacitySchedulerITCase

    ## What is the purpose of the change
    
    Add "Remote connection to [null] failed with java.nio.channels.NotYetConnectedException"
    to the list of whitelisted log statements in YarnTestBase. This logging statement
    seems to appear since we moved from Flakka to Akka 2.4.0.
    
    ## Verifying this change
    
    This change is a trivial rework / code cleanup without any test coverage.
    
    ## Does this pull request potentially affect one of the following parts:
    
      - Dependencies (does it add or upgrade a dependency): (no)
      - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no)
      - The serializers: (no)
      - The runtime per-record code paths (performance sensitive): (no)
      - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
      - The S3 file system connector: (no)
    
    ## Documentation
    
      - Does this pull request introduce a new feature? (no)
      - If yes, how is the feature documented? (not applicable)


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tillrohrmann/flink fixYarnSessionCapacitySchedulerITCase

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/5085.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 #5085
    
----
commit eede21bc1ee335a913d1a49d82d73ce1d0cfe3aa
Author: Till Rohrmann <tr...@apache.org>
Date:   2017-11-27T16:31:28Z

    [FLINK-8161] [tests] Harden YARNSessionCapacitySchedulerITCase
    
    Add "Remote connection to [null] failed with java.nio.channels.NotYetConnectedException"
    to the list of whitelisted log statements in YarnTestBase. This logging statement
    seems to appear since we moved from Flakka to Akka 2.4.0.

----


> 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
>
>
> 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
(v6.4.14#64029)