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

Issue 793616 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: ----



Sign in to add a comment

SitePerProcessBrowserTest.ScrollFocusedEditableElementIntoView is Flaky

Project Member Reported by Findit, Dec 9 2017

Issue description

Cc: maxbogue@chromium.org kolos@chromium.org fdoray@chromium.org
Owner: ekaramad@chromium.org
Tried to revert the culprit but failed: https://chromium-review.googlesource.com/c/chromium/src/+/818371

I'll disable the test.
Project Member

Comment 2 by bugdroid1@chromium.org, Dec 11 2017

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

commit 5b751d4b3032a653ef5a8996cb461038a20936b0
Author: Hajime Hoshi <hajimehoshi@chromium.org>
Date: Mon Dec 11 09:34:12 2017

Disable flaky test SitePerProcessBrowserTest.ScrollFocusedEditableElementIntoView

TBR=hajimehoshi@chromium.org
NOTRY=true

Bug: 793616
Change-Id: Ifeeb75e91ede2aa4225e178a65e1879724441182
Reviewed-on: https://chromium-review.googlesource.com/818944
Reviewed-by: Hajime Hoshi <hajimehoshi@chromium.org>
Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523064}
[modify] https://crrev.com/5b751d4b3032a653ef5a8996cb461038a20936b0/content/browser/site_per_process_browsertest.cc

Labels: -Sheriff-Chromium

Comment 4 by wylieb@chromium.org, Dec 12 2017

Status: Fixed (was: Available)
Status: Assigned (was: Fixed)
Changing to assigned given that the flakiness is not necessarily fixed.

Comment 6 by fdoray@chromium.org, Jan 24 2018

Cc: -fdoray@chromium.org
removing myself from cc since I'm not a sheriff today 
Components: Internals>Sandbox>SiteIsolation
Labels: -Test-Findit-Analyzed -SitePerProcessBrowserTest.ScrollFocusedEditableElementIntoView
Labels: Test-Disabled OS-Android
I am sending a CL to disable the flaky test on Android.
I did look at the log and the failure reason seems legit and mostly happening on Android L device. I will take a look later. Thanks!
Project Member

Comment 11 by bugdroid1@chromium.org, Apr 12 2018

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

commit 63bdc054c4d1b9cda08222e71b81dd4c356a1ab1
Author: Maria Khomenko <mariakhomenko@chromium.org>
Date: Thu Apr 12 18:31:47 2018

Disable flaky test.

SitePerProcessBrowserTest.ScrollFocusedEditableElementIntoView is flaky
across many Android bots.

TBR=kenrb@chromium.org

Bug: 793616
Change-Id: If0f61953ee4dadcf0066f6fdb5ba75929bae10c2
Reviewed-on: https://chromium-review.googlesource.com/1010763
Commit-Queue: Maria Khomenko <mariakhomenko@chromium.org>
Reviewed-by: Ehsan Karamad <ekaramad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550279}
[modify] https://crrev.com/63bdc054c4d1b9cda08222e71b81dd4c356a1ab1/content/browser/site_per_process_browsertest.cc

Project Member

Comment 12 by bugdroid1@chromium.org, Apr 17 2018

Labels: merge-merged-testbranch
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/63bdc054c4d1b9cda08222e71b81dd4c356a1ab1

commit 63bdc054c4d1b9cda08222e71b81dd4c356a1ab1
Author: Maria Khomenko <mariakhomenko@chromium.org>
Date: Thu Apr 12 18:31:47 2018

Disable flaky test.

SitePerProcessBrowserTest.ScrollFocusedEditableElementIntoView is flaky
across many Android bots.

TBR=kenrb@chromium.org

Bug: 793616
Change-Id: If0f61953ee4dadcf0066f6fdb5ba75929bae10c2
Reviewed-on: https://chromium-review.googlesource.com/1010763
Commit-Queue: Maria Khomenko <mariakhomenko@chromium.org>
Reviewed-by: Ehsan Karamad <ekaramad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#550279}
[modify] https://crrev.com/63bdc054c4d1b9cda08222e71b81dd4c356a1ab1/content/browser/site_per_process_browsertest.cc

Trying it locally I get around 10-20% failure rate due to what appears to be a GPU crash:
bort message: '[23620:23656:0515/155052.153482:FATAL:picture_layer_tiling.cc(687)] Check failed: tiling_data_.TileBounds(key.index_x, key.index_y) .Intersects(live_tiles_rect_). 0xb4b6d500 7,15 tile bounds 4915,5251 702x350 live_tiles_rect 4915,5731 4885x4465

Sign in to add a comment