Issue metadata
Sign in to add a comment
|
SiteDetailsBrowserTest.IsolateExtensions timing out |
||||||||||||||||||||||||
Issue descriptionBuild is broken: SiteDetailsBrowserTest.IsolateExtensions in browser_tests on Windows-7-SP1 Revision range: chromium 418801 : 418808 Failing builders: Win7 Tests (dbg)(1): https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20(dbg)(1) [ RUN ] SiteDetailsBrowserTest.IsolateExtensions It passed on the next run in 23 seconds. Perhaps it's just a long-running test that sometimes flakes on debug builders? Maybe the timeout needs to be bumped? [5760:5092:0915/022457:WARNING:persistent_histogram_allocator.cc(485)] Creating the results-histogram inside persistent memory can cause future allocations to crash if that memory is ever released (for testing). [4784:6548:0915/022500:WARNING:persistent_histogram_allocator.cc(485)] Creating the results-histogram inside persistent memory can cause future allocations to crash if that memory is ever released (for testing). [6800:1324:0915/022502:WARNING:persistent_histogram_allocator.cc(485)] Creating the results-histogram inside persistent memory can cause future allocations to crash if that memory is ever released (for testing). [884:2724:0915/022519:WARNING:persistent_histogram_allocator.cc(485)] Creating the results-histogram inside persistent memory can cause future allocations to crash if that memory is ever released (for testing). [5760:5092:0915/022521:INFO:CONSOLE(1)] "Extension One running", source: chrome-extension://lailaoncihdijnjhifieoeliodfhmbaf/script.js (1) [5760:5092:0915/022521:ERROR:interface_registry.cc(99)] Failed to locate a binder for interface: dom_distiller::mojom::DistillabilityService [5760:5092:0915/022523:ERROR:interface_registry.cc(99)] Failed to locate a binder for interface: dom_distiller::mojom::DistillabilityService [5760:4896:0915/022523:WARNING:embedded_test_server.cc(202)] Request not handled. Returning 404: /favicon.ico [3292:6288:0915/022524:WARNING:persistent_histogram_allocator.cc(485)] Creating the results-histogram inside persistent memory can cause future allocations to crash if that memory is ever released (for testing). [5760:5092:0915/022525:ERROR:interface_registry.cc(99)] Failed to locate a binder for interface: dom_distiller::mojom::DistillabilityService [5760:5092:0915/022526:ERROR:interface_registry.cc(99)] Failed to locate a binder for interface: dom_distiller::mojom::DistillabilityService [5760:5092:0915/022527:WARNING:render_frame_host_impl.cc(2059)] OnDidStopLoading was called twice. [5760:5092:0915/022529:WARNING:render_frame_host_impl.cc(2059)] OnDidStopLoading was called twice. [5632:6500:0915/022533:WARNING:persistent_histogram_allocator.cc(485)] Creating the results-histogram inside persistent memory can cause future allocations to crash if that memory is ever released (for testing). [5760:5092:0915/022533:WARNING:render_frame_host_impl.cc(2059)] OnDidStopLoading was called twice. [5760:5092:0915/022534:WARNING:render_frame_host_impl.cc(2059)] OnDidStopLoading was called twice. [2468:6452:0915/022536:WARNING:persistent_histogram_allocator.cc(485)] Creating the results-histogram inside persistent memory can cause future allocations to crash if that memory is ever released (for testing). [3292:6200:0915/022536:ERROR:render_process_impl.cc(109)] WebFrame LEAKED 3 TIMES [5428:4404:0915/022539:WARNING:persistent_histogram_allocator.cc(485)] Creating the results-histogram inside persistent memory can cause future allocations to crash if that memory is ever released (for testing). [121/249] SiteDetailsBrowserTest.IsolateExtensions (TIMED OUT)
,
Sep 20 2016
Copied issue chromium:647181 to issue chromium:648793
,
Apr 3 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dewittj@chromium.org
, Sep 20 2016