memory.top_10_mobile tests are failing on Android Go |
||||
Issue descriptionUnexpected Failures: * memory.top_10_mobile/after_http_en_m_wikipedia_org_wiki_Science * memory.top_10_mobile/after_http_m_intl_taobao_com_group_purchase_html * memory.top_10_mobile/after_http_m_youtube_com_results_q_science * memory.top_10_mobile/after_http_www_amazon_com_gp_aw_s_k_nexus * memory.top_10_mobile/after_http_www_baidu_com_s_word_google * memory.top_10_mobile/after_http_yandex_ru_touchsearch_text_science * memory.top_10_mobile/after_https_m_facebook_com_rihanna * memory.top_10_mobile/after_https_www_google_co_uk_hl_en_q_science Unexpected Flakes: * memory.top_10_mobile/after_http_search_yahoo_com_search__ylt_p_google
,
Jul 21
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16c70b4da40000
,
Jul 21
Done. I've kicked off a functional bisect on after_http_en_m_wikipedia_org_wiki_Science
,
Jul 21
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/16c70b4da40000
,
Jul 21
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1214ebbda40000
,
Jul 22
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/1214ebbda40000 gpu: Hook up activity flags for glProgramBinary for OOPR. by khushalsagar@chromium.org https://chromium.googlesource.com/chromium/src/+/13e510ef164f399158a27396e28c4b31e39107f5 0.1 → 1 (+0.9) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Jul 22
,
Jul 22
Looks like build31-a7--device4 is also consistently failing this test on one story: after_http_en_m_wikipedia_org_wiki_Science. Ned, any idea why that is? Looks like the screenshot doesn't show Chrome at all, but the Messaging app. https://chrome-swarming.appspot.com/task?id=3ed70b2c13351610 https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/60c134dc-8d19-11e8-a94e-0242ac110005
,
Jul 22
(That's in addition to, not related to, the regression in comment 6)
,
Jul 22
Reverting for now, I'll reland after investigating on Monday. (https://chromium-review.googlesource.com/c/chromium/src/+/1146087)
,
Jul 23
Android Go builder is greening again (https://ci.chromium.org/buildbot/chromium.perf.fyi/Android%20Go/) So that revert indeed fixed the failures
,
Jul 23
Thanks for the quick bisect and revert! Closing this regression as fixed, maybe you want to re-open issue 854416 to track your progress when trying to re-land.
,
Jul 23
The following revision refers to this bug: https://chromium.googlesource.com/catapult/+/b97bce9be68065c527e73eb87b7ca1c1b4f58855 commit b97bce9be68065c527e73eb87b7ca1c1b4f58855 Author: Dave Tu <dtu@chromium.org> Date: Mon Jul 23 18:26:48 2018 [pinpoint] Add "Android Go" bot to Pinpoint. Bug: chromium:866251 Change-Id: I50bf314e7a5d84709cda0ec992499f49325ffe83 Reviewed-on: https://chromium-review.googlesource.com/1146148 Reviewed-by: Simon Hatch <simonhatch@chromium.org> Commit-Queue: David Tu <dtu@chromium.org> [modify] https://crrev.com/b97bce9be68065c527e73eb87b7ca1c1b4f58855/dashboard/dashboard/static/pinpoint.html
,
Jul 24
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/dfb3b6e7ddd5d5646352c348760107043f60f602 commit dfb3b6e7ddd5d5646352c348760107043f60f602 Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Date: Tue Jul 24 00:37:14 2018 Roll src/third_party/catapult 1381813c377d..6a1002b4d937 (3 commits) https://chromium.googlesource.com/catapult.git/+log/1381813c377d..6a1002b4d937 git log 1381813c377d..6a1002b4d937 --date=short --no-merges --format='%ad %ae %s' 2018-07-23 simonhatch@chromium.org Dashboard - Add nexus 5x to list of supported for Pinpoint 2018-07-23 dtu@chromium.org [pinpoint] Add "Android Go" bot to Pinpoint. 2018-07-23 benjhayden@chromium.org Upgrade PageStates for V2SPA. Created with: gclient setdep -r src/third_party/catapult@6a1002b4d937 The AutoRoll server is located here: https://catapult-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel BUG= chromium:863995 , chromium:866251 TBR=sullivan@chromium.org Change-Id: I90c1447744e601493ac2c8d2d8258975268d05e9 Reviewed-on: https://chromium-review.googlesource.com/1147068 Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#577375} [modify] https://crrev.com/dfb3b6e7ddd5d5646352c348760107043f60f602/DEPS |
||||
►
Sign in to add a comment |
||||
Comment 1 by nednguyen@chromium.org
, Jul 21