New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 655145 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

TestWebRequestListenerSurvivesReparenting flaky on Ubuntu-12.04

Project Member Reported by msramek@chromium.org, Oct 12 2016

Issue description

On Ubuntu-12.04, in browser_side_navigation_browser_tests, WebViewTests_WebViewTest.Shim_TestWebRequestListenerSurvivesReparenting is somewhat flaky.

Frequency: 3/25 (12%)

Examples:

https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%29%281%29/builds/57961
https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%29%281%29/builds/57966
https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%29%281%29/builds/57971

==============================================

WebViewTests/WebViewTest.Shim_TestWebRequestListenerSurvivesReparenting/1 (run #1):
[ RUN      ] WebViewTests/WebViewTest.Shim_TestWebRequestListenerSurvivesReparenting/1
Xlib:  extension "RANDR" missing on display ":9".
Xlib:  extension "RANDR" missing on display ":9".
[13905:13905:1012/055120:WARNING:persistent_histogram_allocator.cc(502)] Creating the results-histogram inside persistent memory can cause future allocations to crash if that memory is ever released (for testing).
[13905:13905:1012/055120:WARNING:audio_manager.cc(317)] Multiple instances of AudioManager detected
[13905:13905:1012/055120:WARNING:audio_manager.cc(278)] Multiple instances of AudioManager detected
[13905:13905:1012/055120:WARNING:password_store_factory.cc(248)] Using basic (unencrypted) store for password storage. See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_password_storage.md for more information about password storage options.
[1:2:1012/055121:WARNING:persistent_histogram_allocator.cc(502)] Creating the results-histogram inside persistent memory can cause future allocations to crash if that memory is ever released (for testing).
LaunchProcess: failed to execvp:
xdg-desktop-menu
[1:2:1012/055122:WARNING:persistent_histogram_allocator.cc(502)] Creating the results-histogram inside persistent memory can cause future allocations to crash if that memory is ever released (for testing).
LaunchProcess: failed to execvp:
xdg-icon-resource
[13905:14035:1012/055122:WARNING:shell_integration_linux.cc(323)] Could not install icon chrome-pgmfebgjdmlfbgpeceeefkkjkibcjkdg-Default.png at size 512.
LaunchProcess: failed to execvp:
xdg-desktop-menu
[14076:14147:1012/055122:WARNING:persistent_histogram_allocator.cc(502)] Creating the results-histogram inside persistent memory can cause future allocations to crash if that memory is ever released (for testing).
[1:2:1012/055123:WARNING:persistent_histogram_allocator.cc(502)] Creating the results-histogram inside persistent memory can cause future allocations to crash if that memory is ever released (for testing).
[13905:14188:1012/055123:WARNING:simple_synchronous_entry.cc(1054)] Could not open platform files for entry.
[13905:14132:1012/055123:WARNING:embedded_test_server.cc(201)] Request not handled. Returning 404: /favicon.ico
[1:2:1012/055123:WARNING:persistent_histogram_allocator.cc(502)] Creating the results-histogram inside persistent memory can cause future allocations to crash if that memory is ever released (for testing).
[13905:14132:1012/055124:WARNING:embedded_test_server.cc(201)] Request not handled. Returning 404: /favicon.ico
BrowserTestBase received signal: Terminated. Backtrace:
#0 0x7ffef1b0faae base::debug::StackTrace::StackTrace()
#1 0x0000037201c7 content::(anonymous namespace)::DumpStackTraceSignalHandler()
#2 0x7ffedac9d0b0 <unknown>
#3 0x7ffedad4e993 __poll
#4 0x7ffedd7ddff6 <unknown>
#5 0x7ffedd7de124 g_main_context_iteration
#6 0x7ffef1bbe07f base::MessagePumpGlib::Run()
#7 0x7ffef1ba5216 base::MessageLoop::RunHandler()
#8 0x7ffef1c4a9f4 base::RunLoop::Run()
#9 0x0000037b20e3 content::RunThisRunLoop()
#10 0x0000037b206a content::RunMessageLoop()
#11 0x000006534d39 ExtensionTestMessageListener::WaitUntilSatisfied()
#12 0x0000007f225c WebViewTestBase::TestHelper()
#13 0x0000007d5954 WebViewTest_Shim_TestWebRequestListenerSurvivesReparenting_Test::RunTestOnMainThread()
#14 0x000002631698 InProcessBrowserTest::RunTestOnMainThreadLoop()
#15 0x00000371fee3 content::BrowserTestBase::ProxyRunTestOnMainThreadLoop()
#16 0x00000082d959 _ZN4base8internal13FunctorTraitsIM25RenderViewContextMenuBaseFvvEvE6InvokeIP21RenderViewContextMenuJEEEvS4_OT_DpOT0_
#17 0x00000082d881 _ZN4base8internal12InvokeHelperILb0EvE8MakeItSoIRKM25RenderViewContextMenuBaseFvvEJP21RenderViewContextMenuEEEvOT_DpOT0_
#18 0x000003720fd7 _ZN4base8internal7InvokerINS0_9BindStateIMN7content15BrowserTestBaseEFvvEJNS0_17UnretainedWrapperIS4_EEEEEFvvEE7RunImplIRKS6_RKSt5tupleIJS8_EEJLm0EEEEvOT_OT0_NS_13IndexSequenceIJXspT1_EEEE
#19 0x000003720f1c _ZN4base8internal7InvokerINS0_9BindStateIMN7content15BrowserTestBaseEFvvEJNS0_17UnretainedWrapperIS4_EEEEEFvvEE3RunEPNS0_13BindStateBaseE
#20 0x00000081290b base::internal::RunMixin<>::Run()
#21 0x000003272f94 ChromeBrowserMainParts::PreMainMessageLoopRunImpl()
#22 0x0000032719a0 ChromeBrowserMainParts::PreMainMessageLoopRun()
#23 0x7ffee9c5cac1 content::BrowserMainLoop::PreMainMessageLoopRun()
#24 0x7ffee93a00c9 _ZN4base8internal13FunctorTraitsIMN7content12ChildProcessEFvvEvE6InvokeIPS3_JEEEvS5_OT_DpOT0_
#25 0x7ffee9c64dc1 _ZN4base8internal12InvokeHelperILb0EiE8MakeItSoIRKMN7content15BrowserMainLoopEFivEJPS5_EEEiOT_DpOT0_
#26 0x7ffee9c64d67 _ZN4base8internal7InvokerINS0_9BindStateIMN7content15BrowserMainLoopEFivEJNS0_17UnretainedWrapperIS4_EEEEEFivEE7RunImplIRKS6_RKSt5tupleIJS8_EEJLm0EEEEiOT_OT0_NS_13IndexSequenceIJXspT1_EEEE
#27 0x7ffee9c64cac _ZN4base8internal7InvokerINS0_9BindStateIMN7content15BrowserMainLoopEFivEJNS0_17UnretainedWrapperIS4_EEEEEFivEE3RunEPNS0_13BindStateBaseE
#28 0x7ffee921184b base::internal::RunMixin<>::Run()
#29 0x7ffeea7c5aeb content::StartupTaskRunner::RunAllTasksNow()
#30 0x7ffee9c5a900 content::BrowserMainLoop::CreateStartupTasks()
#31 0x7ffee9c67d7d content::BrowserMainRunnerImpl::Initialize()
#32 0x7ffee9c56d2f content::BrowserMain()
#33 0x7ffeeb3780b6 content::RunNamedProcessTypeMain()
#34 0x7ffeeb37a542 content::ContentMainRunnerImpl::Run()
#35 0x7ffeeb377152 content::ContentMain()
#36 0x00000371fbeb content::BrowserTestBase::SetUp()
#37 0x00000262fef4 InProcessBrowserTest::SetUp()
#38 0x00000148a9fd ExtensionBrowserTest::SetUp()
#39 0x000000802d88 WebViewTestBase::SetUp()
#40 0x00000103af7a _ZN7testing8internal12InvokeHelperIvSt5tupleIJEEE12InvokeMethodI14ServiceProcessMS6_FvvEEEvPT_T0_RKS3_
#41 0x0000038bf74e testing::internal::HandleExceptionsInMethodIfSupported<>()
#42 0x0000038b45c3 testing::Test::Run()
#43 0x0000038b4db8 testing::TestInfo::Run()
#44 0x0000038b535a testing::TestCase::Run()
#45 0x0000038ba69c testing::internal::UnitTestImpl::RunAllTests()
#46 0x00000103a58a _ZN7testing8internal12InvokeHelperIbSt5tupleIJEEE12InvokeMethodI20MockServiceIPCServerMS6_FbvEEEbPT_T0_RKS3_
#47 0x0000038c0dee testing::internal::HandleExceptionsInMethodIfSupported<>()
#48 0x0000038ba33f testing::UnitTest::Run()
#49 0x000002644131 RUN_ALL_TESTS()
#50 0x000002643042 base::TestSuite::Run()
#51 0x0000025ea93c ChromeTestSuiteRunner::RunTestSuite()
#52 0x0000025eaa39 ChromeTestLauncherDelegate::RunTestSuite()
#53 0x0000037a4052 content::LaunchTests()
#54 0x0000025eadc9 LaunchChromeTests()
#55 0x0000025ea865 main
#56 0x7ffedac887ed __libc_start_main
#57 0x0000007884a5 <unknown>

==============================================
 
Cc: mark@chromium.org kulshin@chromium.org clamy@chromium.org hayato@chromium.org
+cc sheriffs

browser_side_navigation_browser_tests are very flaky on that bot, but this particular test seems to be flaking only for 1-2 days. I currently don't see anything that recent; if the flake started a bit earlier, https://codereview.chromium.org/2392283005 landed a few days ago touching both browser side navigation and extensions.
 
+clamy@, does this test timeout look familiar, or do you know where to start to investigate?

Comment 2 by clamy@chromium.org, Oct 12 2016

It doesn't look familiar. That said browser-side navigation doesn't fully support WebView yet, so we should just disable it. The CL you mention doesn't touch code used by browser-side navigation, so it can't be the cause.

Comment 3 by clamy@chromium.org, Oct 12 2016

To precise the comment above, when I said we should disable it, I meant for browser-side navigation specifically (ie put it in the test filter).
Ah, right. Most tests in that file are actually already filtered. I'll disable this one as well. Thanks!
Project Member

Comment 5 by bugdroid1@chromium.org, Oct 12 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6634a262d0c108f6149a3eb4bb09b5023bcc7402

commit 6634a262d0c108f6149a3eb4bb09b5023bcc7402
Author: msramek <msramek@chromium.org>
Date: Wed Oct 12 21:33:56 2016

Disable TestWebRequestListenerSurvivesReparenting for browser side navigation

WebViewTests_WebViewTest.Shim_TestWebRequestListenerSurvivesReparenting is
highly flaky (currently 4/25 builds) in browser_side_navigation_browser_tests
on Linux.

As browser side navigation currently doesn't fully support WebView, it should
be just disabled.

TBR=jam@chromium.org,clamy@chromium.org
BUG= 655145 

Review-Url: https://codereview.chromium.org/2416433003
Cr-Commit-Position: refs/heads/master@{#424867}

[modify] https://crrev.com/6634a262d0c108f6149a3eb4bb09b5023bcc7402/testing/buildbot/filters/browser-side-navigation.linux.browser_tests.filter

Project Member

Comment 6 by bugdroid1@chromium.org, Oct 14 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/02c57b69d417d041cfe3162b70a861d6c6e73cc2

commit 02c57b69d417d041cfe3162b70a861d6c6e73cc2
Author: Yoichi Osato <yoichio@chromium.org>
Date: Fri Oct 14 05:56:42 2016

Disable TestWebRequestListenerSurvivesReparenting for browser side navigation

The test is flaky again.

https://uberchromegw.corp.google.com/i/chromium.linux/builders/Linux%20Tests%20%28dbg%
29%281%29

TBR=jam@chromium.org,clamy@chromium.org
BUG= 655145 

Review URL: https://codereview.chromium.org/2416173002 .

Cr-Commit-Position: refs/heads/master@{#425260}

[modify] https://crrev.com/02c57b69d417d041cfe3162b70a861d6c6e73cc2/testing/buildbot/filters/browser-side-navigation.linux.browser_tests.filter

Project Member

Comment 7 by sheriffbot@chromium.org, Oct 16 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Fixed (was: Untriaged)
Looks like the test is re-enabled and is presumably no longer flaky, so closing this issue.

Sign in to add a comment