New issue
Advanced search Search tips

Issue 922131 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

False rejects caused by flakiness in testAccessorySheetHiddenUntilManuallyTriggered

Project Member Reported by erikc...@chromium.org, Jan 15

Issue description

Flakiness dashboard: https://findit-for-me.appspot.com/flake/occurrences?key=ag9zfmZpbmRpdC1mb3ItbWVyrwELEgVGbGFrZSKjAWNocm9taXVtQGNocm9tZV9wdWJsaWNfdGVzdF9hcGtAb3JnLmNocm9taXVtLmNocm9tZS5icm93c2VyLmF1dG9maWxsLmtleWJvYXJkX2FjY2Vzc29yeS5NYW51YWxGaWxsaW5nSW50ZWdyYXRpb25UZXN0I3Rlc3RBY2Nlc3NvcnlTaGVldEhpZGRlblVudGlsTWFudWFsbHlUcmlnZ2VyZWQM

Example build where test flakes both with CL patched in, and on tip of tree [CL patched out]: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-kitkat-arm-rel/162119

"""
I  132.791s run_tests_on_device(06b27f12003c2119)    1) testAccessorySheetHiddenUntilManuallyTriggered(org.chromium.chrome.browser.autofill.keyboard_accessory.ManualFillingIntegrationTest)
I  132.791s run_tests_on_device(06b27f12003c2119)    java.lang.RuntimeException: Waited for the root of the view hierarchy to have window focus and not be requesting layout for over 10 seconds. If you specified a non default root matcher, it may be picking a root that never takes focus. Otherwise, something is seriously wrong. Selected Root:
I  132.791s run_tests_on_device(06b27f12003c2119)    Root{application-window-token=android.view.ViewRootImpl$W@4295f0d8, window-token=android.view.ViewRootImpl$W@4295f0d8, has-window-focus=false, layout-params-type=1, layout-params-string=WM.LayoutParams{(0,0)(fillxfill) sim=#113 ty=1 fl=#1810100 pfl=0x8 wanim=0x10302a1}, decor-view-string=DecorView{id=-1, visibility=VISIBLE, width=1080, height=1776, has-focus=true, has-focusable=true, has-window-focus=false, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=2}}
I  132.791s run_tests_on_device(06b27f12003c2119)    . All Roots:
I  132.791s run_tests_on_device(06b27f12003c2119)    Root{application-window-token=android.view.ViewRootImpl$W@4295f0d8, window-token=android.view.ViewRootImpl$W@4295f0d8, has-window-focus=false, layout-params-type=1, layout-params-string=WM.LayoutParams{(0,0)(fillxfill) sim=#113 ty=1 fl=#1810100 pfl=0x8 wanim=0x10302a1}, decor-view-string=DecorView{id=-1, visibility=VISIBLE, width=1080, height=1776, has-focus=true, has-focusable=true, has-window-focus=false, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=false, is-selected=false, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=2}}
"""


 
Screen Shot 2019-01-15 at 1.28.24 PM.png
230 KB View Download
Cc: fhorschig@chromium.org rsorokin@chromium.org

Comment 2 by rsorokin@chromium.org, Jan 16 (6 days ago)

Cc: se...@chromium.org
Components: UI>Browser>Autofill

Comment 3 by fhorschig@chromium.org, Jan 18 (4 days ago)

Labels: mfill-ch
Available and selected roots are identical and the test doesn't set the root to something special. 

It seems like "Otherwise, something is seriously wrong." is a likely (and unhelpful) explanation.

Sign in to add a comment