New issue
Advanced search Search tips

Issue 894147 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

blink_perf.svg/SierpinskiCarpet.html failing on chromium.perf/Android Nexus5 Perf

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Oct 10

Issue description

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

blink_perf.svg/SierpinskiCarpet.html  in performance_test_suite failing on chromium.perf/Android Nexus5 Perf

Looks like first known failure is ~r595917, known good is around r595433. I'll kick off a bisect.

Builders failed on: 
- Android Nexus5 Perf: 
  https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/Android%20Nexus5%20Perf


 
Cc: f...@opera.com
Also, looks like this is failing on 5X too.
Project Member

Comment 4 by bugdroid1@chromium.org, Oct 10

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

commit 309c6b258fe1dae108d85d0d6cfbd5149d585272
Author: Charlie Andrews <charliea@chromium.org>
Date: Wed Oct 10 18:22:57 2018

Disabling failing SierpinskiCarpet on N5 and N5X

NOTRY=true
TBR=nednguyen@chromium.org
CC=kouhei@chromium.org, fs@opera.com

Bug: 894147
Change-Id: Ief219684e6e0aa2c106815541a794391e6a61096
Reviewed-on: https://chromium-review.googlesource.com/c/1274185
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598410}
[modify] https://crrev.com/309c6b258fe1dae108d85d0d6cfbd5149d585272/tools/perf/expectations.config

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/15f7f8dae40000
I still think that this revision range is right. Going to kick off another job.
📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/161dc387e40000
Owner: kouhei@chromium.org
Status: Assigned (was: Available)
Leaving this open but assigning to benchmark owners: the story is definitely flaky, but I'm unable to pinpoint an exact change where that behavior started.

Sign in to add a comment