[MESOS-467] AllocatorTest.FrameworkExited is flaky

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.15.0
• Assignee: Vinod Kone
• Reporter: Thomas Marshall
• Created: 09/May/13 23:34
• Updated: 18/Oct/13 00:40
• Resolved: 18/Oct/13 00:40

Description

Note: Google Test filter = TaskFinished-
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from AllocatorTest/0, where TypeParam = mesos::internal::master::HierarchicalAllocatorProcess<mesos::internal::master::DRFSorter, mesos::internal::master::DRFSorter>
[ RUN ] AllocatorTest/0.TaskFinished
../../src/tests/allocator_tests.cpp:1098: Failure
Mock function called more times than expected - returning directly.
Function call: resourceOffers(0x7fff58d85380, @0x10b1089e8

{ 224-byte object <30-C0 74-09 01-00 00-00 00-00 00-00 00-00 00-00 00-75 05-15 EC-7F 00-00 00-90 04-15 EC-7F 00-00 70-90 04-15 EC-7F 00-00 20-22 03-15 EC-7F 00-00 88-C2 05-15 EC-7F 00-00 04-00 00-00 04-00 00-00 ... F8-C2 05-15 EC-7F 00-00 01-00 00-00 01-00 00-00 04-00 00-00 EC-7F 00-00 C0-74 05-15 EC-7F 00-00 18-C3 05-15 EC-7F 00-00 04-00 00-00 04-00 00-00 04-00 00-00 01-00 00-00 00-00 00-00 0F-00 00-00> }

)
Expected: to be called once
Actual: called twice - over-saturated and active
Segmentation fault: 11