system_health.common_mobile failing on multiple builders |
||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of simonhatch@chromium.org system_health.common_mobile failing on multiple builders Builders failed on: - Android Nexus5 Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf - Android Nexus5X WebView Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20WebView%20Perf - Android Nexus6 WebView Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20WebView%20Perf - Android Nexus7v2 Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus7v2%20Perf
,
Jan 2 2018
Unexpected Failures: * system_health.common_mobile/background:news:nytimes * system_health.common_mobile/load:games:spychase
,
Jan 3 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e477ebe3033b5a960f39e910a9d439b5af931b5a commit e477ebe3033b5a960f39e910a9d439b5af931b5a Author: Simon <simonhatch@chromium.org> Date: Wed Jan 03 17:31:18 2018 Disable stories on system_health.common_mobile Android TBR=nednguyen@google.com NOTRY=true Bug: 798536 Change-Id: Ie01236ca17cd385de37e3f97730258aed9832544 Reviewed-on: https://chromium-review.googlesource.com/849013 Reviewed-by: Simon Hatch <simonhatch@chromium.org> Commit-Queue: Simon Hatch <simonhatch@chromium.org> Cr-Commit-Position: refs/heads/master@{#526727} [modify] https://crrev.com/e477ebe3033b5a960f39e910a9d439b5af931b5a/tools/perf/expectations.config
,
Jun 8 2018
,
Jul 19
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14a85f71a40000
,
Jul 19
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/13fc6e71a40000
,
Jul 19
Kicked off two perf try jobs to see if we can get a better idea of if these are still failing and what the failures might be.
,
Jul 20
📍 Job complete. See results below. https://pinpoint-dot-chromeperf.appspot.com/job/13fc6e71a40000
,
Jul 21
📍 Job complete. See results below. https://pinpoint-dot-chromeperf.appspot.com/job/14a85f71a40000
,
Jul 23
The flaky tryjob failures (unable to find a bot, jwt credentials) seem unrelated to the benchmark. I think it's fine to re-enable.
,
Jul 24
Reenable CL is up and going through the CQ now: https://chromium-review.googlesource.com/c/chromium/src/+/1143450
,
Jul 24
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/dccb439b9748ae93c2109b7769ae66b3d86083bd commit dccb439b9748ae93c2109b7769ae66b3d86083bd Author: Charlie Andrews <charliea@chromium.org> Date: Tue Jul 24 14:46:15 2018 Reenable nytimes and spychase on Android Based on a try job in the linked bug, it looks like these stories are no longer failing. TBR=sullivan@chromium.org Bug: 798536 Change-Id: I44a6d819fa0fea6dc71b76d0189933b9009d3c78 Reviewed-on: https://chromium-review.googlesource.com/1143450 Reviewed-by: Charlie Andrews <charliea@chromium.org> Commit-Queue: Charlie Andrews <charliea@chromium.org> Cr-Commit-Position: refs/heads/master@{#577533} [modify] https://crrev.com/dccb439b9748ae93c2109b7769ae66b3d86083bd/tools/perf/expectations.config
,
Jul 30
|
||||
►
Sign in to add a comment |
||||
Comment 1 by simonhatch@chromium.org
, Jan 2 2018