Make sure advancing non-zero time delta for mock timer in testScrollLatencyFromTimeline
This is a speculative fix for the flaky test RenderingStatsUnitTest.testScrollLatencyFromTimeline (crbug.com/358673) I am not sure about the root cause and can't repro this locally. Buy inspecting the code I feel there could be problems if the default timer.Advance() advances 0ms. So lets always pass in explicit low & high parameters into timer.Advance(low, high) and see if this fix the flaky test. Note: the root cause could have been fixed by https://src.chromium.org/viewvc/chrome?revision=261034&view=revision This is CL could be just a nice add-on. BUG=358673 TEST=unittests RenderingStatsUnitTest.* pass. Review URL: https://codereview.chromium.org/220113008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261464 0039d316-1c4b-4281-b951-d872f2087c98
Showing
Please register or sign in to comment