Fix flaky test DeepScanningReportingTest.ProcessesResponseCorrectly.
This test tried to use a service whose factory is null in test mode. It would work if run standalone because the factory was _also_ not properly registered on startup, so the testing factory would never be set to null. However, if run in a batch with other browser tests, a previous test's access to the factory would register it; the next browser startup would null its testing factory; and then this test would crash. This fixes both problems: registers the factory, and sets a non-null testing factory. Bug: none Change-Id: I877cb9b7c58e82de17888b52d7d6ddc34f5bec27 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2133626Reviewed-by:David Bertoni <dbertoni@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#755866}
Showing
Please register or sign in to comment