FrameTokenMessageQueue Debugging of Flaky Tests
FrameTokenMessageQueue is setup to kill misbehaving Renderer processes, when frame submission happens out of order. This has typically been a side effect of other more serious bugs, and used to help identify the cause. However FullscreenInteractiveBrowserTest.NotifyFullscreenAcquired has been flaking with this failure. In order to get a better idea of what is the cause I'm looking to add extra stateful info, along with two earlier DCHECKs. I'm also re-enabling the test in order to get reproductions, as I haven't been able to reproduce locally. TBR=ellyjones@chromium.org TEST=FullscreenInteractiveBrowserTest.NotifyFullscreenAcquired Bug: 1087744 Change-Id: I470c33e3ca1c76abd810d551bf02dcfc9a0eaa51 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2239677Reviewed-by:Jonathan Ross <jonross@chromium.org> Reviewed-by:
kylechar <kylechar@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#777458}
Showing
Please register or sign in to comment