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 2013/03/07 03:06:13 UTC
[jira] [Created] (MESOS-383) AllocatorTest/0.FrameworkExited test
is broken
Benjamin Mahler created MESOS-383:
-------------------------------------
Summary: AllocatorTest/0.FrameworkExited test is broken
Key: MESOS-383
URL: https://issues.apache.org/jira/browse/MESOS-383
Project: Mesos
Issue Type: Bug
Reporter: Benjamin Mahler
Assignee: Vinod Kone
[ RUN ] AllocatorTest/0.FrameworkExited
GMOCK WARNING:
Uninteresting mock function call - returning directly.
Function call: error(0x7fff6fbf75c8, @0x7fadf0b154f0 "Framework failed over")
Stack trace:
../../src/tests/allocator_tests.cpp:830: Failure
Failed
Waited too long for 'resourceOffersTrigger2'
GMOCK WARNING:
Uninteresting mock function call - returning directly.
Function call: statusUpdate(0x7fff6fbf6f88, @0x7fadf0b0ab50 56-byte object <90-69 0E-11 01-00 00-00 00-00 00-00 00-00 00-00 50-04 B1-F0 AD-7F 00-00 00-05 B1-F0 AD-7F 00-00 D0-FF 0E-11 01-00 00-00 05-00 00-00 00-00 00-00 07-00 00-00 35-2D 33-36>)
Stack trace:
../../src/tests/allocator_tests.cpp:817: Failure
Mock function called more times than expected - returning directly.
Function call: resourceOffers(0x7fff6fbf6f88, @0x111d09bd8 { 224-byte object <10-7A 0E-11 01-00 00-00 00-00 00-00 00-00 00-00 80-73 B1-F0 AD-7F 00-00 50-1D B0-F0 AD-7F 00-00 C0-7A B1-F0 AD-7F 00-00 E0-03 B1-F0 AD-7F 00-00 08-0B B1-F0 AD-7F 00-00 04-00 00-00 04-00 00-00 ... 78-0B B1-F0 AD-7F 00-00 01-00 00-00 01-00 00-00 04-00 00-00 01-00 00-00 80-48 B1-F0 AD-7F 00-00 00-00 00-00 00-00 00-20 6D-0D 0B-DF FA-07 00-40 03-00 1B-EC 65-EF 00-00 00-00 00-00 0F-00 00-00> })
Expected: to be called once
Actual: called twice - over-saturated and active
--
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