Specific test failure:
mMeshManagerTest.SetupFeasibilityTest_SchedulesTestIfBusy
ap-daemons-0.0.3-r3759: [0124/223839:INFO:state_machine.h(123)] State Machine MeshManager initialized at state MESH_ENABLED
ap-daemons-0.0.3-r3759: [0124/223839:INFO:state_machine.cc(47)] State Machine MeshManager received event OWNERS_INTERSECT during state MESH_ENABLED
ap-daemons-0.0.3-r3759: [0124/223839:INFO:state_machine.cc(33)] State Machine MeshManager transitioning from MESH_ENABLED to MESH_ALLOWED
ap-daemons-0.0.3-r3759: [0124/223839:INFO:state_machine.cc(47)] State Machine MeshManager received event SETUP_FEASIBILITY_TEST during state MESH_ALLOWED
ap-daemons-0.0.3-r3759: [0124/223839:INFO:state_machine.cc(47)] State Machine MeshManager received event SCHEDULE_FEASIBILITY_TEST during state MESH_ALLOWED
ap-daemons-0.0.3-r3759: ../../../../../../../tmp/portage/chromeos-base/ap-daemons-0.0.3-r3759/work/ap-daemons-0.0.3/platform/ap-daemons/controller/mesh_manager_test.cc:330: Failure
ap-daemons-0.0.3-r3759: Expected: mesh_manager_->feasibility_test_scheduled_
ap-daemons-0.0.3-r3759: Which is: true
ap-daemons-0.0.3-r3759: To be equal to: false
ap-daemons-0.0.3-r3759: [0;31m[ FAILED ] [mMeshManagerTest.SetupFeasibilityTest_SchedulesTestIfBusy (45 ms)
https://luci-milo.appspot.com/buildbot/chromeos/gale-paladin/5104
Comment 1 by shapiroc@chromium.org
, Jan 25 2018