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

Issue 803465 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
█ ashleymarie@google.com
mythria@chromium.org
u...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

v8.browsing_mobile/browse:chrome:newtab failing on chromium.perf/Android Nexus5 Perf

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Jan 18 2018 
Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of ashleymarie@google.com

v8.browsing_mobile/browse:chrome:newtab failing on chromium.perf/Android Nexus5 Perf

Builders failed on: 
- Android Nexus5 Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf
- Android Nexus5 Perf: 
  https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf
Project Member

Comment 1 by bugdroid1@chromium.org, Jan 18 2018 

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

commit bf287201f4e56fb6540169208ab711d5b0132741
Author: Ashley Enstad <ashleymarie@chromium.org>
Date: Thu Jan 18 19:56:49 2018

Disabling browse:chrome:newtab on mobile

browse:chrome:newtab stories failing on Android Nexus5 Perf for
system_health.common_mobile, system_health.memory_mobile,
v8.browsing_mobile, and v8.browsing_mobile-future

Bug: 803465,  803461 , 803462
Change-Id: I1d9f7f3df779de3ad12037db16a37b517f7944b3
Reviewed-on: https://chromium-review.googlesource.com/873991
Commit-Queue: Ashley Enstad <ashleymarie@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#530238}
[modify] https://crrev.com/bf287201f4e56fb6540169208ab711d5b0132741/tools/perf/expectations.config

Comment 2 by mythria@chromium.org, Jan 25 2018

Labels: v8-benchmarks

Comment 3 by dtapu...@chromium.org, Jun 8 2018

Components: Speed>Benchmarks>Waterfall
►

Sign in to add a comment