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

Issue 687258 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Feb 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

memory.top_10_mobile_stress failure on chromium.perf at 446356:446465

Project Member Reported by eakuefner@chromium.org, Jan 31 2017

Issue description

Revision range first seen: 446356:446465
Link to failing step log: https://build.chromium.org/p/chromium.perf/builders/Mac%2010.11%20Perf/builds/301/steps/memory.top_10_mobile_stress%20on%20Intel%20GPU%20on%20Mac%20on%20Mac-10.11

Test is failing on Mac, Windows, Linux.

If the test is disabled, please downgrade to Pri-2.

 
Labels: -Pri-1 Pri-2
Disable CL is landing, so lowering priority.

Please note that this test is also failing on reference, but I didn't disable it for ref since apparently we don't do that anymore.
Project Member

Comment 2 by bugdroid1@chromium.org, Jan 31 2017

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

commit b6f1374b024b68b909ffb632b5a8c184391476bf
Author: eakuefner <eakuefner@chromium.org>
Date: Tue Jan 31 20:08:41 2017

[BotHealth] Disable memory.top_10_mobile_stress on Win/Mac/Linux

BUG= 687258 

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

[modify] https://crrev.com/b6f1374b024b68b909ffb632b5a8c184391476bf/tools/perf/benchmarks/memory.py

Cc: nednguyen@chromium.org
Wat? This is a mobile benchmark, shouldn't be running on desktop platforms at all.
Cc: mikec...@chromium.org
Status: Fixed (was: Untriaged)
Ah, I know what happened. The benchmark was only implicitly disabled on desktop because those platforms "can't launch the DeskClock app"; but we removed that dependency on r446434 with mikecase's work.

I've filed go/catabug/3176 to track the fix of the underlying issue (the decorator should not be needed there in the first place), and sent out https://codereview.chromium.org/2668923002 to do a bit of cleanup on the decorators and bugs they point to.
Cc: sullivan@chromium.org
 Issue 687002  has been merged into this issue.
Issue 691661 has been merged into this issue.
Labels: Performance-Memory

Sign in to add a comment