You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2012/09/28 20:43:10 UTC
[jira] [Created] (MESOS-286) AllocatorTest is flaky
Benjamin Mahler created MESOS-286:
-------------------------------------
Summary: AllocatorTest is flaky
Key: MESOS-286
URL: https://issues.apache.org/jira/browse/MESOS-286
Project: Mesos
Issue Type: Bug
Reporter: Benjamin Mahler
Assignee: Vinod Kone
Looks like we didn't catch all the bad EXPECTs.
[ RUN ] AllocatorTest/0.TaskFinished
2012-09-28 11:24:26,006:2178(0x2b6a5d58f700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:39076] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2012-09-28 11:24:26,006:2178(0x2b6a5d790700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:39076] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
../../src/tests/allocator_tests.cpp:1140: Failure
Mock function called more times than expected - returning directly.
Function call: resourcesChanged(@0x2b6a54151af8 201209281124-16842879-54998-2178-0000, @0x2b6a54151ad8 default, @0x2b6a54151aa0 { cpus=1, mem=256 })
Expected: to be called twice
Actual: called 3 times - over-saturated and active
2012-09-28 11:24:27,261:2178(0x2b6a5cd8b700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:33484] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
2012-09-28 11:24:27,264:2178(0x2b6a5cb8a700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:33484] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
[ FAILED ] AllocatorTest/0.TaskFinished, where TypeParam = mesos::internal::master::HierarchicalAllocatorProcess<mesos::internal::master::DRFSorter, mesos::internal::master::DRFSorter> (2029 ms)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MESOS-286) AllocatorTest is flaky
Posted by "Vinod Kone (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MESOS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone resolved MESOS-286.
------------------------------
Resolution: Cannot Reproduce
> AllocatorTest is flaky
> ----------------------
>
> Key: MESOS-286
> URL: https://issues.apache.org/jira/browse/MESOS-286
> Project: Mesos
> Issue Type: Bug
> Reporter: Benjamin Mahler
> Assignee: Vinod Kone
>
> Looks like we didn't catch all the bad EXPECTs.
> [ RUN ] AllocatorTest/0.TaskFinished
> 2012-09-28 11:24:26,006:2178(0x2b6a5d58f700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:39076] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
> 2012-09-28 11:24:26,006:2178(0x2b6a5d790700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:39076] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
> ../../src/tests/allocator_tests.cpp:1140: Failure
> Mock function called more times than expected - returning directly.
> Function call: resourcesChanged(@0x2b6a54151af8 201209281124-16842879-54998-2178-0000, @0x2b6a54151ad8 default, @0x2b6a54151aa0 { cpus=1, mem=256 })
> Expected: to be called twice
> Actual: called 3 times - over-saturated and active
> 2012-09-28 11:24:27,261:2178(0x2b6a5cd8b700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:33484] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
> 2012-09-28 11:24:27,264:2178(0x2b6a5cb8a700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:33484] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
> [ FAILED ] AllocatorTest/0.TaskFinished, where TypeParam = mesos::internal::master::HierarchicalAllocatorProcess<mesos::internal::master::DRFSorter, mesos::internal::master::DRFSorter> (2029 ms)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira