Fix and re-enable background:tools:gmail |
||||||
Issue descriptionHector, when you have some time, could you look into this one? Issue 664505 has some links to logs where this test was failing.
,
Apr 6 2017
Ran a try-job with 20 repeats here: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/1489 One of them failed with "ERR_TO_MANY_REDIRECTS": https://console.developers.google.com/m/cloudstorage/b/chromium-telemetry/o/profiler-file-id_19-2017-04-06_05-15-0079395.png Full log: https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Ftryserver.chromium.perf%2Fandroid_nexus5X_perf_bisect%2F1489%2F%2B%2Frecipes%2Fsteps%2FRunning_WITH_patch%2F0%2Fsteps%2FPerformance_Test__With_Patch__1_of_1%2F0%2Flogs%2FFailure_Output%2F0 Ned, I remember there were some bugs investigating causes and possible solutions to that problem with WPR? Also, not sure why it stopped after a single failure and didn't complete all pageset repeats?
,
Apr 6 2017
I think it could be https://github.com/chromium/web-page-replay/issues/78
,
Sep 7 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8103668869a11dbcfb383ac6380c46a32bdede6a commit 8103668869a11dbcfb383ac6380c46a32bdede6a Author: Juan A. Navarro Perez <perezju@chromium.org> Date: Thu Sep 07 09:21:36 2017 [tools/perf] Reenable background:tools:gmail on Android The story might be more lucky now after the WprGo migration. TBR=nednguyen@google.com Bug: 676336 Change-Id: Iecec0ef5dff0ec85266ce2f23b0bce5b7c9215b4 Reviewed-on: https://chromium-review.googlesource.com/653057 Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org> Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org> Cr-Commit-Position: refs/heads/master@{#500253} [modify] https://crrev.com/8103668869a11dbcfb383ac6380c46a32bdede6a/tools/perf/page_sets/system_health/expectations.py
,
Sep 7 2017
,
Dec 13 2017
This is still disabled on v8 benchmark
,
Dec 14 2017
,
Dec 14 2017
,
Dec 14
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 17
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by perezju@chromium.org
, Apr 5 2017Owner: perezju@chromium.org