flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tillrohrmann <...@git.apache.org>
Subject [GitHub] flink issue #2257: [FLINK-4152] Allow re-registration of TMs at resource man...
Date Fri, 22 Jul 2016 17:27:55 GMT
Github user tillrohrmann commented on the issue:

    At the moment I'm a little bit clueless why the test case errors occur. One test case
error is probably related to concurrency issues in the `TestingLeaderRetrievalService`. I've
fixed them but the error is still occurring in my local builds on Travis. Here the problem
is that maven does not use the installed flink-runtim_2.10-tests.jar which contains the updated
`TestingLeaderRetrievalService` but instead it downloads the the flink-runtime test jar from
the snapshot repository which contains the code with the concurrency issue.
    The other test issue I've seen is that the `flink-yarn-tests` sometimes fail because they
contain no a
    2016-07-22 12:01:31,308 ERROR akka.remote.EndpointWriter                             
      - AssociationError [akka.tcp://flink@] <- [akka.tcp://flink@]:
Error [Shut down address: akka.tcp://flink@] [
    akka.remote.ShutDownAssociation: Shut down address: akka.tcp://flink@
    Caused by: akka.remote.transport.Transport$InvalidAssociationException: The remote system
terminated the association because it is shutting down.
    in the logs. Since the test checks for exception as a word, it fails. I cannot yet explain
why this association error now occurs but apparently didn't occur before.

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 infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message