[jira] [Updated] (MESOS-5759) ProcessRemoteLinkTest.RemoteUseStaleLink and RemoteStaleLinkRelink are flaky

["Artem Harutyunyan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Artem Harutyunyan updated MESOS-5759:
-------------------------------------
    Sprint: Mesosphere Sprint 38, Mesosphere Sprint 39  (was: Mesosphere Sprint 38)

> ProcessRemoteLinkTest.RemoteUseStaleLink and RemoteStaleLinkRelink are flaky
> ----------------------------------------------------------------------------
>
>                 Key: MESOS-5759
>                 URL: https://issues.apache.org/jira/browse/MESOS-5759
>             Project: Mesos
>          Issue Type: Bug
>          Components: libprocess, test
>    Affects Versions: 1.0.0
>            Reporter: Joseph Wu
>            Assignee: Joseph Wu
>              Labels: libprocess, mesosphere
>
> {{ProcessRemoteLinkTest.RemoteUseStaleLink}} and {{ProcessRemoteLinkTest.RemoteStaleLinkRelink}} are failing occasionally with the error:
> {code}
> [ RUN      ] ProcessRemoteLinkTest.RemoteStaleLinkRelink
> WARNING: Logging before InitGoogleLogging() is written to STDERR
> I0630 07:42:34.661110 18888 process.cpp:1066] libprocess is initialized on 172.17.0.2:56294 with 16 worker threads
> E0630 07:42:34.666393 18765 process.cpp:2104] Failed to shutdown socket with fd 7: Transport endpoint is not connected
> /mesos/3rdparty/libprocess/src/tests/process_tests.cpp:1059: Failure
> Value of: exitedPid.isPending()
>   Actual: false
> Expected: true
> [  FAILED  ] ProcessRemoteLinkTest.RemoteStaleLinkRelink (56 ms)
> {code}
> There appears to be a race between establishing a socket connection and the test calling {{::shutdown}} on the socket.  Under some circumstances, the {{::shutdown}} may actually result in failing the future in {{SocketManager::link_connect}} error and thereby trigger {{SocketManager::close}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)