Issue metadata
Sign in to add a comment
|
"SitePerProcessBrowserTest.FrameOwnerPropertiesPropagationScrolling" is flaky |
||||||||||||||||||||||||
Issue description"SitePerProcessBrowserTest.FrameOwnerPropertiesPropagationScrolling" 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 9 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyTQsSBUZsYWtlIkJTaXRlUGVyUHJvY2Vzc0Jyb3dzZXJUZXN0LkZyYW1lT3duZXJQcm9wZXJ0aWVzUHJvcGFnYXRpb25TY3JvbGxpbmcM. 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
,
Jan 18 2018
Navid, is this the same as the test failures you've seen recently? The crash in the test is below. (I think it's different than the failures kenrb@ is investigating, but feel free to correct me.) base::debug::BreakDebugger [0x028BBE0C+12] logging::LogMessage::~LogMessage [0x02826EBF+815] blink::PaintLayer::HitTestLayer [0x0445426B+129] blink::PaintLayer::HitTest [0x044540D6+376] blink::LayoutView::HitTestNoLifecycleUpdate [0x0433C197+255] blink::LayoutView::HitTest [0x0433BF5C+48] blink::EventHandler::HitTestResultAtPoint [0x041E9AFF+473] blink::WebFrameWidgetImpl::HitTestResultForRootFramePos [0x04D35420+150] blink::WebFrameWidgetImpl::CoreHitTestResultAt [0x04D33DD5+197] blink::WebFrameWidgetImpl::HitTestResultAt [0x04D33CE9+41] content::RenderWidgetInputHandler::GetFrameSinkIdAtPoint [0x0482E613+157] content::RenderWidget::GetFrameSinkIdAtPoint [0x04795A5C+22] content::InputTargetClientImpl::FrameSinkIdAt [0x047B5A0B+43] viz::mojom::InputTargetClientStubDispatch::AcceptWithResponder [0x01517EC8+258] viz::mojom::InputTargetClientStub<mojo::RawPtrImplRefTraits<viz::mojom::InputTargetClient> >::AcceptWithResponder [0x047B5AAE+62] mojo::InterfaceEndpointClient::HandleValidatedMessage [0x026381F3+539] mojo::FilterChain::Accept [0x0263F6B3+131] mojo::InterfaceEndpointClient::HandleIncomingMessage [0x02638FC8+106] mojo::internal::MultiplexRouter::ProcessIncomingMessage [0x02635522+698] mojo::internal::MultiplexRouter::Accept [0x026350A7+295] mojo::FilterChain::Accept [0x0263F6B3+131] mojo::Connector::ReadSingleMessage [0x0263CE35+367] mojo::Connector::ReadAllAvailableMessages [0x0263D519+87] mojo::Connector::OnHandleReadyInternal [0x0263D3E4+126] base::internal::Invoker<base::internal::BindState<void (__thiscall content::TouchActionBrowserTest::*)(enum content::SyntheticGesture::Result),base::internal::UnretainedWrapper<content::TouchActionBrowserTest> >,void __cdecl(enum content::SyntheticGesture [0x0266357F+15] mojo::SimpleWatcher::DiscardReadyState [0x037BC798+24] base::internal::Invoker<base::internal::BindState<bool (__cdecl*)(base::RepeatingCallback<bool __cdecl(void)> const &,content::NotificationSource const &,content::NotificationDetails const &),base::RepeatingCallback<bool __cdecl(void)> >,bool __cdecl(cont [0x01588F03+19] mojo::SimpleWatcher::OnHandleReady [0x02CC45C0+224] base::internal::Invoker<base::internal::BindState<void (__thiscall mojo::SimpleWatcher::*)(int,unsigned int,mojo::HandleSignalsState const &),base::WeakPtr<mojo::SimpleWatcher>,int,unsigned int,mojo::HandleSignalsState>,void __cdecl(void)>::Run [0x02CC484A+58] base::debug::TaskAnnotator::RunTask [0x028B6657+231] blink::scheduler::TaskQueueManager::ProcessTaskFromWorkQueue [0x024D05ED+561] blink::scheduler::TaskQueueManager::DoWork [0x024D005A+602] base::internal::Invoker<base::internal::BindState<void (__thiscall content::VideoCaptureHost::*)(int),base::WeakPtr<content::VideoCaptureHost>,int>,void __cdecl(void)>::RunOnce [0x029D356B+59] base::debug::TaskAnnotator::RunTask [0x028B6657+231] blink::scheduler::internal::ThreadControllerImpl::DoWork [0x024D4CA5+197] base::internal::Invoker<base::internal::BindState<void (__thiscall content::VideoEncoderShim::*)(enum media::VideoEncodeAccelerator::Error),base::WeakPtr<content::VideoEncoderShim>,enum media::VideoEncodeAccelerator::Error>,void __cdecl(void)>::RunOnce [0x02527D21+49] base::debug::TaskAnnotator::RunTask [0x028B6657+231] base::internal::IncomingTaskQueue::RunTask [0x028DA9A9+105] base::MessageLoop::RunTask [0x02856547+519] base::MessageLoop::DeferOrRunPendingTask [0x028568B0+160] base::MessageLoop::DoWork [0x02856AF8+520] base::MessagePumpDefault::Run [0x028DC951+177] base::MessageLoop::Run [0x02855EE9+169] base::RunLoop::Run [0x0284195C+204] content::RendererMain [0x047A4DA5+501] content::RunNamedProcessTypeMain [0x015FBE88+148] content::ContentMainRunnerImpl::Run [0x015FC3F8+280] service_manager::Main [0x0396F1E9+677] content::ContentMain [0x015FBD9B+51] content::LaunchTests [0x025AC158+284] main [0x049B19D9+65] __scrt_common_main_seh [0x051BF93A+248] (f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:283) BaseThreadInitThunk [0x74BF338A+18] RtlInitializeExceptionChain [0x771B9F72+99] RtlInitializeExceptionChain [0x771B9F45+54]
,
Jan 18 2018
,
Jan 18 2018
This looks like issue 798476 again. It is causing test flaking in an increasingly large set of our --site-per-process browser tests (apparently only on Windows for some reason?), and nobody has managed a local reproduction yet. That is a high priority to be fixed right now.
,
Jan 18 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f9d2806b7b0f11e738d3a4c44ad731134060aad4 commit f9d2806b7b0f11e738d3a4c44ad731134060aad4 Author: Sorin Jianu <sorin@chromium.org> Date: Thu Jan 18 23:08:27 2018 Disable flaky test SitePerProcessBrowserTest.FrameOwnerPropertiesPropagationScrolling. TBR: creis Bug: 803628 Change-Id: Ieece385b25dd5976704b490f35425b3955759ad5 Reviewed-on: https://chromium-review.googlesource.com/875173 Reviewed-by: Sorin Jianu <sorin@chromium.org> Reviewed-by: Charlie Reis <creis@chromium.org> Commit-Queue: Sorin Jianu <sorin@chromium.org> Cr-Commit-Position: refs/heads/master@{#530326} [modify] https://crrev.com/f9d2806b7b0f11e738d3a4c44ad731134060aad4/content/browser/site_per_process_browsertest.cc
,
Jan 19 2018
,
Jan 19 2018
,
Jan 22 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/cacd0085c363f70055d6a20a51ad670a1681c411 commit cacd0085c363f70055d6a20a51ad670a1681c411 Author: Ken Buchanan <kenrb@chromium.org> Date: Mon Jan 22 20:38:12 2018 Re-enable various SitePerProcessBrowserTests A bug that was causing flakes in many OOPIF-based browser tests was fixed in r530669. This re-enables several tests that were disabled due to that bug. TBR=msramek@chromium.org Bug: 798476 , 803641 , 803628 , 803627 , 802828 , 802281 Change-Id: Ib37c6761cd1ee46d8e49ef393db21209935862dd Reviewed-on: https://chromium-review.googlesource.com/879101 Commit-Queue: Ken Buchanan <kenrb@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#530981} [modify] https://crrev.com/cacd0085c363f70055d6a20a51ad670a1681c411/chrome/browser/ui/content_settings/content_setting_bubble_model_browsertest.cc [modify] https://crrev.com/cacd0085c363f70055d6a20a51ad670a1681c411/content/browser/site_per_process_browsertest.cc |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sorin@chromium.org
, Jan 18 2018Labels: -Sheriff-Chromium
Owner: creis@chromium.org