[Extensions] SearchApiTest tabs.onUpdated() instead of tabs.query().
The purpose of this CL is flake mitigation. This paragraph relates to running each apitest 3000x apiece. These are crashes even when the test is only succeed(). The flake rate is around 1.3% with unrelated crashes. Relevant tests seem to have a similar heuristic. Dave mentioned it might be good to file a bug for it. Flakiness may have been caused by instantly checking tab url. This CL leverages a TabListener object to await tab updates. Once a tab has been updated, the url can be chekced more reliably. A queue of depth one was implemented here not expecting more than that. For the normal test, didPerformQuery cannot be run first/parallel due to race condition errors where two succeed occur simultaneously when the test framework was only expecting one, causing error. These tests pass locally, as did the previous version. The previous version was run with `--gtest_repeat=20`, in addition to this version. Bug: 1119846 Change-Id: Idcb3a3aa82e4ce9df7a36da9a69071634c1a6ff1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368147 Commit-Queue: Solomon Kinard <solomonkinard@chromium.org> Reviewed-by:David Bertoni <dbertoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#802748}
Showing
Please register or sign in to comment