Fix FrameSinkVideoCaptureDevice tests
Fixes the behavior of some of these tests with https://chromium-review.googlesource.com/c/chromium/src/+/1145692 applied. That CL changes how Mojo bindings dispatch messages, but only timing (not ordering) is changed. This can break subtle test expecations, as is the case here. This change replaces use of deprecated RunAllPendingInMessageLoop with either RunLoop usage or TestBrowserThreadBundle::RunIOThreadUntilIdle. In the latter case, in order to achieve synchronization parity with the code before this change, note that it is also necessary to have WAIT_FOR_DEVICE_TASKS wait for the UI thread to idle after the IO thread has idled, due to the way RunAllPendingInMessageLoop worked. Bug: 895693 Change-Id: I15552766245eda0bdce141c40643ee4b44cc90a8 Reviewed-on: https://chromium-review.googlesource.com/c/1286432 Commit-Queue: Yuri Wiitala <miu@chromium.org> Reviewed-by:Yuri Wiitala <miu@chromium.org> Cr-Commit-Position: refs/heads/master@{#600601}
Showing
Please register or sign in to comment