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

Issue 666420 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Nov 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: ----
Type: ----



Sign in to add a comment

webkit_tests failing on chromium.webkit/WebKit Android (Nexus4)

Project Member Reported by est...@chromium.org, Nov 17 2016

Issue description

webkit_tests failing on chromium.webkit/WebKit Android (Nexus4)

Type: build-failure

Builders failed on: 
- WebKit Android (Nexus4): 
  https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Android%20%28Nexus4%29


this has been failing consistently for a couple days with no obvious culprit (even from the initial blamelist)
 

Comment 1 by est...@chromium.org, Nov 17 2016

Cc: dominickn@chromium.org yusukes@chromium.org derat@chromium.org mgiuca@chromium.org qyears...@chromium.org samans@chromium.org lukasza@chromium.org ti...@chromium.org lgcheng@google.com ben@chromium.org
Labels: OS-Android
first failed here - https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Android%20%28Nexus4%29/builds/57004

cc'ing blamelist authors
Hm, it looks like the only CLs in third_party/WebKit were mine, although I believe that nothing committed in that range should have affected layout test results; two CLs in that range that mention android are:

r432309 Replace the use of WindowAndroid with Tab in permissions code.
r432310 Android: support multiple displays on C++ side
Cc: -lukasza@chromium.org
My r432314 only changed browser tests - it shouldn't have affected content_shell and/or layout tests.

Comment 4 by derat@chromium.org, Nov 17 2016

Cc: -derat@chromium.org
I'm pretty sure that my OWNERS file change was unrelated.
The failing tests don't look like they invoke a permission prompt, which was my Android change.

Comment 6 by ti...@chromium.org, Nov 17 2016

r432310 Android: support multiple displays on C++ side
could lead to failure if this is a crash.

Comment 7 by est...@chromium.org, Nov 18 2016

timav, do you mind reverting to see if it resolves the issue?

Comment 8 by ti...@chromium.org, Nov 18 2016

Created revert in https://codereview.chromium.org/2514633002/

Comment 9 by mgiuca@chromium.org, Nov 18 2016

The revert landed:
commit ece04082b79fd30261b48ad895e7f05beeda7823
Author: timav <timav@chromium.org>
Date: Fri Nov 18 04:38:33 2016
Cr-Commit-Position: refs/heads/master@{#433108}

Will keep an eye on this.
Labels: -Sheriff-Chromium
Remove from sheriff queue (if it continues to be a problem it will come up again in SOM).
Status: Fixed (was: Available)

Sign in to add a comment