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

Issue 816587 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1%-1.9% regression in memory.top_10_mobile at 538567:538712

Project Member Reported by tdres...@chromium.org, Feb 26 2018

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Feb 26 2018

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=816587

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=e2b0f40b45f1a95094fa51a41dae4a690f95b709bfa97bc41920999294a0daf6


Bot(s) for this bug's original alert(s):

android-nexus6
android-nexus7v2
android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 26 2018

Cc: dpranke@chromium.org iannucci@chromium.org tandrii@chromium.org
Owner: iannucci@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12a71ba8440000

[test_env.py] Reland: Warm up vpython virtualenv cache on swarming task shards by iannucci@chromium.org
https://chromium.googlesource.com/chromium/src/+/2181305023501418e22e421c3ad7a2ecb0322b4d

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Owner: ----
Status: Available (was: Assigned)
Cc: -tandrii@chromium.org
Cc: dtu@chromium.org
Status: Untriaged (was: Available)
+dtu, can you add this to the list of bisects to re-rerun when we can patch over breakages?

Comment 7 by sullivan@google.com, May 31 2018

Status: WontFix (was: Untriaged)
These recovered. If we need to find the culprit, we can re-run with https://chromium-review.googlesource.com/c/catapult/+/1077070 pinned.

Sign in to add a comment