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

Issue 842175 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

rasterize_and_record_micro.top_25/.../espn.html in rasterize_and_record_micro.top_25 failing on chromium.perf/Android One Perf

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, May 11 2018

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of charliea@chromium.org

rasterize_and_record_micro.top_25/.../espn.html in rasterize_and_record_micro.top_25 failing on chromium.perf/Android One Perf

Builders failed on: 
- Android One Perf: 
  https://ci.chromium.org/buildbot/chromium.perf/Android%20One%20Perf

Looks like this has been going on for a long time (>50 builds). The first failure I see is 547587 and it looks like a safe passing build is around 547587. Going to disable and kick off a bisect.
 
Project Member

Comment 2 by bugdroid1@chromium.org, May 11 2018

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

commit 61d320f10b71323aef0757ecadbafdf81c9bae1d
Author: Charlie Andrews <charliea@chromium.org>
Date: Fri May 11 15:07:51 2018

Disable rasterize_and_record_micro.top_25/espn

The test has been flaky for some time now.

NOTRY=true
TBR=nednguyen@chromium.org
CC=wkorman@chromium.org,vmpstr@chromium.org

Bug: 842175
Change-Id: I857bbc9e9077d1378d59cdc14d7a03a7e1a67057
Reviewed-on: https://chromium-review.googlesource.com/1055593
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#557882}
[modify] https://crrev.com/61d320f10b71323aef0757ecadbafdf81c9bae1d/tools/perf/expectations.config

Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 11 2018

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12a7cea0240000
Link to relevant flakiness dashboard: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=rasterize_and_record_micro.top_25&builder=chromium.perf%3AAndroid%20One%20Perf

Sigh: I used the same "good" and "bad" revisions when launching the bisect. Going to try with different revisions this time. 547857 does indeed look like a bad revision, but I think that 545722 is a reasonable good revision.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, May 14 2018

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/110fec37c40000
Cc: dtu@chromium.org
Components: Speed>Benchmarks>Waterfall
Labels: -Pri-1 Pri-2
Just a heads up, this appears to be having the same problem as I mentioned in https://bugs.chromium.org/p/chromium/issues/detail?id=842163#c4.

Sign in to add a comment