Fix flaky EngagementTimeUtilTest test
The test still used System.currentTimeMillis() which could very rarely return a different value even between just a few instructions. Change-Id: I8cc649771cec6506b28decba91bd74a1ed1a7e03 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1929084Reviewed-by:Min Qin <qinmin@chromium.org> Commit-Queue: David Trainor <dtrainor@chromium.org> Cr-Commit-Position: refs/heads/master@{#718399}
Showing
Please register or sign in to comment