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

Issue 812615 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-02-16
OS: Android
Pri: 2
Type: ----



Sign in to add a comment

blink_perf.canvas failing on chromium.perf/Android Nexus 5, 5X and Nexus5X WebView Perf

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Feb 15 2018

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of ashleymarie@google.com

blink_perf.canvas failing on chromium.perf/Android Nexus5X WebView Perf

Builders failed on: 
- Android Nexus5X WebView Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20WebView%20Perf

Looks like the last time blink_perf.canvas passed on Nexus5X WebView Perf was February 2nd...

A bisect may be difficult to run do to the number of exception runs since around when it started failing


 
Cc: charliea@chromium.org
 Issue 812777  has been merged into this issue.
Owner: junov@chromium.org
Status: Assigned (was: Available)
Summary: blink_perf.canvas failing on chromium.perf/Android Nexus 5, 5X andNexus5X WebView Perf (was: blink_perf.canvas failing on chromium.perf/Android Nexus5X WebView Perf)
I strongly suspect based on the flakiness dashboard (https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=blink_perf.canvas&builder=chromium.perf%3AAndroid%20Nexus5X%20Perf) that the first failing revision was 533941 and the last passing revision was 533838. I'm going to kick a bisect off in this range.
Components: Speed>Benchmarks>Waterfall
Labels: OS-Android
Summary: blink_perf.canvas failing on chromium.perf/Android Nexus 5, 5X and Nexus5X WebView Perf (was: blink_perf.canvas failing on chromium.perf/Android Nexus 5, 5X andNexus5X WebView Perf)
There also seems to have been a major regression of the metric in this range, so I think that it's likely.
NextAction: 2018-02-16
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Feb 15 2018

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14e77af3840000
The NextAction date has arrived: 2018-02-16
Project Member

Comment 9 by bugdroid1@chromium.org, Feb 16 2018

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

commit 250fb9b35311a6d66d9d00a3696be9ccd77da062
Author: Charlie Andrews <charliea@chromium.org>
Date: Fri Feb 16 15:42:53 2018

Disable failing blink_perf.canvas story on 5, 5X, and 5X webview

TBR=ashleymarie@chromium.org
NOTRY=true

Bug: 812615
Change-Id: Ib89c68b30e3b0f33eded7e35572dd71208d60a4d
Reviewed-on: https://chromium-review.googlesource.com/922788
Reviewed-by: Ashley Enstad <ashleymarie@chromium.org>
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537309}
[modify] https://crrev.com/250fb9b35311a6d66d9d00a3696be9ccd77da062/tools/perf/expectations.config

Bisect was unable to repro a failure - kicking this over to the benchmark owner. junov@, could you maybe try kicking off a bisect with a wider revision range?
Project Member

Comment 11 by bugdroid1@chromium.org, Feb 20 2018

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

commit 846149dd2f73b6114e2204fdc3ca356bdc50dfcb
Author: Khushal <khushalsagar@chromium.org>
Date: Tue Feb 20 21:07:51 2018

Revert "Disable failing blink_perf.canvas story on 5, 5X, and 5X webview"

This reverts commit 250fb9b35311a6d66d9d00a3696be9ccd77da062.

Reason for revert: The bug which caused the failure has been fixed.

Original change's description:
> Disable failing blink_perf.canvas story on 5, 5X, and 5X webview
> 
> TBR=ashleymarie@chromium.org
> NOTRY=true
> 
> Bug: 812615
> Change-Id: Ib89c68b30e3b0f33eded7e35572dd71208d60a4d
> Reviewed-on: https://chromium-review.googlesource.com/922788
> Reviewed-by: Ashley Enstad <ashleymarie@chromium.org>
> Reviewed-by: Charlie Andrews <charliea@chromium.org>
> Commit-Queue: Charlie Andrews <charliea@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#537309}

TBR=charliea@chromium.org,ashleymarie@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 812615
Change-Id: I2cb330d935fdf42d41c00e05637e3dee9e22989f
Reviewed-on: https://chromium-review.googlesource.com/927202
Reviewed-by: Khushal <khushalsagar@chromium.org>
Reviewed-by: Ashley Enstad <ashleymarie@chromium.org>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537880}
[modify] https://crrev.com/846149dd2f73b6114e2204fdc3ca356bdc50dfcb/tools/perf/expectations.config

What CL was ultimately responsible for these failures?
 Issue 812744  has been merged into this issue.
Cc: -junov@chromium.org
Owner: ----
Status: Available (was: Assigned)

Sign in to add a comment