+chfremer in case you have any insight or cycles to help look into this

I will look at it today.

And just to clarify, these failures appear when applying this CL[1]. The CL does not break any guarantees made by Mojo bindings, but it can affect the timing of arbitrary events. The failures therefore strongly imply that incorrect ordering assumptions being made somewhere, and this has been the case for all other blocking bugs which have been fixed so far.

[1] https://chromium-review.googlesource.com/c/chromium/src/+/1145692

CL with a fix for the test is up:
https://chromium-review.googlesource.com/c/chromium/src/+/1167968

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7ffdde3135707d317126d4abad6d44ac81048681

commit 7ffdde3135707d317126d4abad6d44ac81048681
Author: Christian Fremerey <chfremer@chromium.org>
Date: Wed Aug 08 22:02:55 2018

Fix video capture unit test making wrong assumption about event ordering

Bug:  872065 
Change-Id: If0de2e5cb8470e604bc97f1c3689ae8972888e6c
Reviewed-on: https://chromium-review.googlesource.com/1167968
Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Christian Fremerey <chfremer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#581702}
[modify] https://crrev.com/7ffdde3135707d317126d4abad6d44ac81048681/services/video_capture/texture_virtual_device_mojo_adapter_unittest.cc