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

Till Toenshoff commented on MESOS-1257:
---------------------------------------

Quick update;
- the MC as ECP shim appears to be working fine now. 
- most of the "SlaveRecoveryTests" are adapted now to stop interfering with the 
EC due to Clock::pause uses
- will start pushing out RRs tomorrow 

As of now, the following tests do not pass yet: "PartitionedSlave" and 
"MasterFailover".

So expect a bunch of RRs upcoming: 
- EC-fixes on recovery and destroy
- MC as ECP shim aka C++ test-containerizer
- adapted SlaveRecoveryTests

> ExternalContainerizerTest.Launch is flaky
> -----------------------------------------
>
>                 Key: MESOS-1257
>                 URL: https://issues.apache.org/jira/browse/MESOS-1257
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Jie Yu
>            Assignee: Till Toenshoff
>
> {noformat}
> [----------] 1 test from ExternalContainerizerTest
> [ RUN      ] ExternalContainerizerTest.Launch
> 2014-04-28 
> 17:04:14,345:44634(0x7f94deffd700):ZOO_ERROR@handle_socket_error_msg@1697: 
> Socket [127.0.0.1:52535] zk retcode=-4, errno=111(Connection refused): server 
> refused to accept the client
> 2014-04-28 
> 17:04:17,681:44634(0x7f94deffd700):ZOO_ERROR@handle_socket_error_msg@1697: 
> Socket [127.0.0.1:52535] zk retcode=-4, errno=111(Connection refused): server 
> refused to accept the client
> 2014-04-28 
> 17:04:21,018:44634(0x7f94deffd700):ZOO_ERROR@handle_socket_error_msg@1697: 
> Socket [127.0.0.1:52535] zk retcode=-4, errno=111(Connection refused): server 
> refused to accept the client
> ../../../mesos/src/tests/external_containerizer_test.cpp:202: Failure
> Failed to wait 10secs for status
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to