"TaskManagerOOPIFBrowserTest.NavigateToSiteWithSubframeToOriginalSite/0" is flaky |
|||||
Issue description"TaskManagerOOPIFBrowserTest.NavigateToSiteWithSubframeToOriginalSite/0" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyUQsSBUZsYWtlIkZUYXNrTWFuYWdlck9PUElGQnJvd3NlclRlc3QuTmF2aWdhdGVUb1NpdGVXaXRoU3ViZnJhbWVUb09yaWdpbmFsU2l0ZS8wDA. 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 17 2017
https://codereview.chromium.org/2630773002 is a culprit [ RUN ] TaskManagerOOPIFBrowserTest.NavigateToSiteWithSubframeToOriginalSite/0 Xlib: extension "RANDR" missing on display ":99". [11219:11219:0316/091917.076756:WARNING:audio_manager.cc(295)] Multiple instances of AudioManager detected [11219:11219:0316/091917.076798:WARNING:audio_manager.cc(254)] Multiple instances of AudioManager detected [11219:11219:0316/091917.133429:WARNING:password_store_factory.cc(247)] 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. [11219:11219:0316/091917.369882:FATAL:desktop_window_tree_host_x11.cc(836)] Check failed: !is_active || window_mapped_in_server_. #0 0x000002e42107 base::debug::StackTrace::StackTrace() #1 0x000002e5ab2b logging::LogMessage::~LogMessage() #2 0x000003dca255 views::DesktopWindowTreeHostX11::IsActive() #3 0x000003dc740f views::DesktopWindowTreeHostX11::AfterActivationStateChanged() #4 0x000003dca0f1 views::DesktopWindowTreeHostX11::Activate() #5 0x000003da53f2 views::FocusManager::SetFocusedViewWithReason() #6 0x000003db9ef9 views::Widget::SetInitialFocus() #7 0x000003e0309b views::DesktopNativeWidgetAura::ShowWithWindowState() #8 0x000003db82e1 views::Widget::Show() #9 0x000005437147 task_manager::TaskManagerView::Show() #10 0x000000ff229d TaskManagerBrowserTest::ShowTaskManager() #11 0x0000010000c9 TaskManagerOOPIFBrowserTest_NavigateToSiteWithSubframeToOriginalSite_Test::RunTestOnMainThread() #12 0x000002f1b79f InProcessBrowserTest::RunTestOnMainThreadLoop() #13 0x000003534316 content::BrowserTestBase::ProxyRunTestOnMainThreadLoop() #14 0x00000335b729 ChromeBrowserMainParts::PreMainMessageLoopRunImpl() #15 0x00000335a5e1 ChromeBrowserMainParts::PreMainMessageLoopRun() #16 0x000001ab0295 content::BrowserMainLoop::PreMainMessageLoopRun() #17 0x000001e9f176 content::StartupTaskRunner::RunAllTasksNow() #18 0x000001aae12b content::BrowserMainLoop::CreateStartupTasks() #19 0x000001ab3e7e content::BrowserMainRunnerImpl::Initialize() #20 0x000001aab5a8 content::BrowserMain() #21 0x000002e1f6d3 content::RunNamedProcessTypeMain() #22 0x000002e203e6 content::ContentMainRunnerImpl::Run() #23 0x000002e1ea70 content::ContentMain() #24 0x000003533c20 content::BrowserTestBase::SetUp() #25 0x000002f19de1 InProcessBrowserTest::SetUp() #26 0x000003d0a00e testing::Test::Run() #27 0x000003d0abd0 testing::TestInfo::Run() #28 0x000003d0af47 testing::TestCase::Run() #29 0x000003d12197 testing::internal::UnitTestImpl::RunAllTests() #30 0x000003d11e17 testing::UnitTest::Run() #31 0x000002f2cf41 base::TestSuite::Run() #32 0x000002e34428 ChromeTestSuiteRunner::RunTestSuite() #33 0x00000356328c content::LaunchTests() #34 0x000002e343a7 main #35 0x7f3a824c9f45 __libc_start_main #36 0x000000603bb1 <unknown>
,
Mar 17 2017
,
Mar 17 2017
,
Mar 17 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9b35aa2cb18ff78d6cfc843f0e9414ccb6c22150 commit 9b35aa2cb18ff78d6cfc843f0e9414ccb6c22150 Author: thomasanderson <thomasanderson@google.com> Date: Fri Mar 17 19:45:27 2017 X11: Fix test flakes related to window focus This CL removes code intended to fix "some tests depending on a window being IsActive() immediately after an Activate()". After https://codereview.chromium.org/2630773002, all of these cases should be using WidgetActivationWaiter, so this is unnecessary. This was causing DCHECK(!is_active || window_mapped_in_server_) to fail. In addition, XSetInputFocus on an unmapped window will fail, so supress the error in this case. This is the same thing GTK does https://github.com/GNOME/gtk/blob/7ade6e3f4668220f0fa1382944a87e63691ad9ad/gdk/x11/gdkwindow-x11.c#L1904 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_chromium_dbg_ng BUG= 701722 , 701921 , 701706 , 701485 , 701484 , 700692 , 700683 , 700661 , 701886 R=erg@chromium.org Review-Url: https://codereview.chromium.org/2756183003 Cr-Commit-Position: refs/heads/master@{#457859} [modify] https://crrev.com/9b35aa2cb18ff78d6cfc843f0e9414ccb6c22150/ui/views/widget/desktop_aura/desktop_window_tree_host_x11.cc
,
Mar 20 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by chromium...@appspot.gserviceaccount.com
, Mar 16 2017