Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(659)

Issue 1804413004: Disable blink_perf.canvas on Android One (Closed)

Created:
4 years, 9 months ago by petrcermak
Modified:
4 years, 9 months ago
Reviewers:
dshwang, Sami
CC:
chromium-reviews, telemetry-reviews_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Disable blink_perf.canvas on Android One Rationale: The benchmark is consistently failing on the "Android One Perf (2)" bot (see the associated bug). BUG=593973 TBR=skyostil CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:winx64_10_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq;tryserver.chromium.perf:linux_perf_cq Committed: https://crrev.com/69b38e03d4714e45603211a9b8b198d39b6e9546 Cr-Commit-Position: refs/heads/master@{#381741}

Patch Set 1 #

Total comments: 3

Patch Set 2 : Use IsSvelte() instead #

Unified diffs Side-by-side diffs Delta from patch set Stats (+4 lines, -0 lines) Patch
M tools/perf/benchmarks/blink_perf.py View 1 1 chunk +4 lines, -0 lines 0 comments Download

Messages

Total messages: 20 (10 generated)
petrcermak
PTAL. Thanks, Petr
4 years, 9 months ago (2016-03-17 13:31:17 UTC) #3
petrcermak
https://codereview.chromium.org/1804413004/diff/1/tools/perf/benchmarks/blink_perf.py File tools/perf/benchmarks/blink_perf.py (right): https://codereview.chromium.org/1804413004/diff/1/tools/perf/benchmarks/blink_perf.py#newcode183 tools/perf/benchmarks/blink_perf.py:183: return '4560MMX' in possible_browser.platform.GetDeviceTypeName() See ro.product.model in https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf%20%282%29/builds/2461/steps/provision_devices/logs/stdio
4 years, 9 months ago (2016-03-17 13:32:41 UTC) #4
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1804413004/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1804413004/1
4 years, 9 months ago (2016-03-17 13:33:11 UTC) #7
Sami
lgtm. https://codereview.chromium.org/1804413004/diff/1/tools/perf/benchmarks/blink_perf.py File tools/perf/benchmarks/blink_perf.py (right): https://codereview.chromium.org/1804413004/diff/1/tools/perf/benchmarks/blink_perf.py#newcode183 tools/perf/benchmarks/blink_perf.py:183: return '4560MMX' in possible_browser.platform.GetDeviceTypeName() On 2016/03/17 13:32:41, petrcermak ...
4 years, 9 months ago (2016-03-17 13:48:36 UTC) #8
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1804413004/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1804413004/20001
4 years, 9 months ago (2016-03-17 15:12:13 UTC) #12
petrcermak
On 2016/03/17 13:48:36, Sami wrote: > lgtm. > > https://codereview.chromium.org/1804413004/diff/1/tools/perf/benchmarks/blink_perf.py > File tools/perf/benchmarks/blink_perf.py (right): > ...
4 years, 9 months ago (2016-03-17 15:12:31 UTC) #13
commit-bot: I haz the power
Committed patchset #2 (id:20001)
4 years, 9 months ago (2016-03-17 17:53:12 UTC) #15
commit-bot: I haz the power
Patchset 2 (id:??) landed as https://crrev.com/69b38e03d4714e45603211a9b8b198d39b6e9546 Cr-Commit-Position: refs/heads/master@{#381741}
4 years, 9 months ago (2016-03-17 17:54:43 UTC) #17
dshwang
https://codereview.chromium.org/1804413004/diff/1/tools/perf/benchmarks/blink_perf.py File tools/perf/benchmarks/blink_perf.py (right): https://codereview.chromium.org/1804413004/diff/1/tools/perf/benchmarks/blink_perf.py#newcode183 tools/perf/benchmarks/blink_perf.py:183: return '4560MMX' in possible_browser.platform.GetDeviceTypeName() On 2016/03/17 13:48:36, Sami wrote: ...
4 years, 9 months ago (2016-03-18 14:24:23 UTC) #19
Sami
4 years, 9 months ago (2016-03-18 15:34:55 UTC) #20
Message was sent while issue was closed.
On 2016/03/18 14:24:23, dshwang wrote:
> Does it exclude only Android One?

No, it excludes all Svelte devices like you said. We only have the One on the
waterfall, and generally the test failures are triggered by the lack of memory,
so it is usually fine to blanket-disable tests for all of Svelte.

Powered by Google App Engine
This is Rietveld 408576698