New issue
Advanced search Search tips

Issue 776092 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

loading.mobile story GoogleRedirectToGoogleJapan failing on chromium.perf/Android One Perf

Project Member Reported by charliea@google.com, Oct 18 2017

Issue description

loading.mobile failing on chromium.perf/Android One Perf

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

This test has been failing since at least 10/5, so I'm not able to see the revision range at which it started failing. I'll go ahead and disable, but will leave investigation to the benchmark owners.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Oct 18 2017

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

commit 416280b838a2ce26521fc55feef7ee22d544d08d
Author: Charlie Andrews <charliea@google.com>
Date: Wed Oct 18 22:05:08 2017

Disable loading.mobile GoogleRedirectToGoogleJapan on Android One

TBR=rnephew@chromium.org

Bug: 776092
Change-Id: Ie0e1cc1cd0f33adff4ca9049ea181d7e05a3f020
Reviewed-on: https://chromium-review.googlesource.com/726275
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Reviewed-by: rnephew <rnephew@chromium.org>
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#509892}
[modify] https://crrev.com/416280b838a2ce26521fc55feef7ee22d544d08d/tools/perf/benchmarks/loading.py

Cc: -kouhei@chromium.org
Owner: kouhei@chromium.org
Actually, turns out that I can look back further than 10/5. This benchmark was still failing flakily as far ago as 9/22. It looks like between 9/22 and 10/5, this story failed about 34 times. Between 9/8 and 9/21, it failed 3 times. So it looks like this story has been flaky for a really long time, but something has happened to make it a lot flakier. I see it failing as far back as 8/21, at which point I stopped looking back further. I'll let owners investigate.
Labels: Pri-2
Setting defect without priority to Pri-2.

Sign in to add a comment