"WebViewAPITest.TestExecuteScriptIsAbortedWhenWebViewSourceIsChanged" is flaky |
|||
Issue description"WebViewAPITest.TestExecuteScriptIsAbortedWhenWebViewSourceIsChanged" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyTgsSBUZsYWtlIkNXZWJWaWV3QVBJVGVzdC5UZXN0RXhlY3V0ZVNjcmlwdElzQWJvcnRlZFdoZW5XZWJWaWV3U291cmNlSXNDaGFuZ2VkDA. Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
,
Mar 20 2017
[ RUN ] WebViewAPITest.TestExecuteScriptIsAbortedWhenWebViewSourceIsChanged [30538:30538:0320/003037.924916:7185597006:WARNING:audio_manager.cc(295)] Multiple instances of AudioManager detected [30538:30538:0320/003037.924998:7185597047:WARNING:audio_manager.cc(254)] Multiple instances of AudioManager detected [30538:30538:0320/003037.952271:7185624323:ERROR:proxy_service.cc(1519)] ProxyConfigService for ChromeOS should be created in profile_io_data.cc::CreateProxyConfigService and this should be used only for examples. [30538:30538:0320/003038.284104:7185956156:INFO:CONSOLE(723)] "1. Performing initial navigation.", source: chrome-extension://plbodpbgifcoilpboopmflfjcpfdiiob/main.js (723) [30538:30538:0320/003038.400225:7186072278:INFO:CONSOLE(695)] "2. Inject script to trigger a guest-initiated navigation.", source: chrome-extension://plbodpbgifcoilpboopmflfjcpfdiiob/main.js (695) [30538:30538:0320/003038.402532:7186074582:INFO:CONSOLE(702)] "3. Listening for the load that will be started as a result of 2.", source: chrome-extension://plbodpbgifcoilpboopmflfjcpfdiiob/main.js (702) [30538:30538:0320/003038.436839:7186108891:INFO:CONSOLE(706)] "4. Attempting to inject script into about:blank. This is expected to fail.", source: chrome-extension://plbodpbgifcoilpboopmflfjcpfdiiob/main.js (706) [30538:30538:0320/003038.442758:7186114808:INFO:CONSOLE(711)] "5. Verify that executeScript has, indeed, failed.", source: chrome-extension://plbodpbgifcoilpboopmflfjcpfdiiob/main.js (711) [30538:30538:0320/003038.443567:7186115617:INFO:CONSOLE(41)] "assertion failed: null != red", source: chrome-extension://plbodpbgifcoilpboopmflfjcpfdiiob/main.js (41) ../../extensions/browser/guest_view/web_view/web_view_apitest.cc:175: Failure Value of: done_listener.WaitUntilSatisfied() Actual: false Expected: true [ FAILED ] WebViewAPITest.TestExecuteScriptIsAbortedWhenWebViewSourceIsChanged, where TypeParam = and GetParam() = (583 ms) Assigning to paulmeyer@chromium.org for triaging.
,
Apr 4 2017
This has the same root cause as bug 703727, you might consider merging.
,
Apr 4 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Mar 20 2017