Revert "[Extensions] Add a test for webRequestBlocking listeners that are killed"
This reverts commit dee92446. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 594509 as the culprit for flakes in the build cycles as shown on: https://findit-for-me.appspot.com/waterfall/flake/flake-culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vZGVlOTI0NDZmNzhhYzcwMzYxZGU1OWFlMjI0OTM5YmU4ZjgyMzk4Zgw Sample Failed Build: https://ci.chromium.org/buildbot/chromium.win/Win%207%20Tests%20x64%20%281%29/43524 Sample Failed Step: network_service_browser_tests Sample Flaky Test: WebRequestUnresponsiveListenerTest.WebRequestListenerNeverResponds/0 Original change's description: > [Extensions] Add a test for webRequestBlocking listeners that are killed > > Add a test that exercises behavior for a webRequestBlocking listener > that never returns, and then the tab is closed. Do this with two > flavors: > - A listener in the extension's background page, where the > RenderProcessHost is shutdown. > - A listener in an extension tab, which is then closed. > > Verify that in both cases, navigation is unblocked when the extension > listener goes away. > > Inspired by, but not in any way a fix for, https://crbug.com/877543. > > Change-Id: Id918d6d5f7bf5d8235f1386ef48838bffaa1b50c > Reviewed-on: https://chromium-review.googlesource.com/1188942 > Commit-Queue: Devlin <rdevlin.cronin@chromium.org> > Reviewed-by: Nasko Oskov <nasko@chromium.org> > Reviewed-by: Karan Bhatia <karandeepb@chromium.org> > Cr-Commit-Position: refs/heads/master@{#594509} Change-Id: I2c9ebb07e448747ca7f83e51470e1d5e96edc9bd No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 889701 Reviewed-on: https://chromium-review.googlesource.com/1247527 Cr-Commit-Position: refs/heads/master@{#594550}
Showing
Please register or sign in to comment