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

Issue 629163 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression

Blocking:
issue 589726



Sign in to add a comment

load:news:washingtonpost failure in v8.browsing_mobile and system_health.memory_mobile on chromium.perf

Project Member Reported by charliea@chromium.org, Jul 18 2016

Issue description

Owner: petrcermak@chromium.org
Status: Assigned (was: Untriaged)
Assigning to petrcermak@
Project Member

Comment 2 by bugdroid1@chromium.org, Jul 18 2016

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

commit 53e7aad1a0f82edbe0f51d99c2c532a96b03a3fa
Author: charliea <charliea@chromium.org>
Date: Mon Jul 18 21:52:46 2016

[perfbot sheriff] Disable v8.browsing_mobile and sh.memory_mobile on N9

TBR=petrcermak@chromium.org
BUG= 629163 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq

Review-Url: https://codereview.chromium.org/2155163003
Cr-Commit-Position: refs/heads/master@{#406109}

[modify] https://crrev.com/53e7aad1a0f82edbe0f51d99c2c532a96b03a3fa/tools/perf/benchmarks/system_health.py
[modify] https://crrev.com/53e7aad1a0f82edbe0f51d99c2c532a96b03a3fa/tools/perf/benchmarks/v8_browsing.py

Blocking: 589726
Cc: u...@chromium.org chrome-system-health-eng@google.com petrcermak@chromium.org
Labels: Hotlist-SystemHealth
Owner: u...@chromium.org
Summary: load:news:washingtonpost failure in v8.browsing_mobile and system_health.memory_mobile on chromium.perf (was: v8.browsing_mobile and system_health.memory_mobile failure on chromium.perf)
These are all due to the following failure on load:news:washingtonpost (in addition to failures due to  issue 628631 ):

EvaluateException: Error: Cannot find element: using selector ".close"
    at Error (native)
    at callback (<anonymous>:7:19)
    at <anonymous>:11:16
    at <anonymous>:12:9
    at Object.InjectedScript._evaluateOn (<anonymous>:875:140)
    at Object.InjectedScript._evaluateAndWrap (<anonymous>:808:34)
    at Object.InjectedScript.evaluate (<anonymous>:664:21)

Given that the story was added in r405212, which falls within the range where the failure first appeared, I'm assigning this to ulan@.

Comment 4 by u...@chromium.org, Jul 19 2016

Trying to reproduce on N9
Project Member

Comment 5 by bugdroid1@chromium.org, Jul 19 2016

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

commit 50adac87a62954be18180cbf74590a54a9d70dd4
Author: ulan <ulan@chromium.org>
Date: Tue Jul 19 20:35:31 2016

[system health] Fix load:news:washingtonpost and browse:news:washingtonpost on Nexus9.

Washingtonpost popup window on Nexus9 does not have "Close" button.
This patch checks for the presence of the button before clicking it.

BUG= 629163 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq

Review-Url: https://codereview.chromium.org/2159253002
Cr-Commit-Position: refs/heads/master@{#406372}

[modify] https://crrev.com/50adac87a62954be18180cbf74590a54a9d70dd4/tools/perf/benchmarks/system_health.py
[modify] https://crrev.com/50adac87a62954be18180cbf74590a54a9d70dd4/tools/perf/benchmarks/v8_browsing.py
[modify] https://crrev.com/50adac87a62954be18180cbf74590a54a9d70dd4/tools/perf/page_sets/system_health/browsing_stories.py
[modify] https://crrev.com/50adac87a62954be18180cbf74590a54a9d70dd4/tools/perf/page_sets/system_health/loading_stories.py

Comment 6 by u...@chromium.org, Jul 20 2016

Status: Fixed (was: Assigned)
 Issue 629983  has been merged into this issue.

Sign in to add a comment