load:tools:drive timing out during LoginGoogleAccount |
|||
Issue description
The story has recently started failing timing out while:
File "/b/swarming/w/ir/tools/perf/page_sets/login_helpers/google_login.py", line 73, in LoginGoogleAccount
action_runner.WaitForElement(text='My Account')
On the 5X upstream bots, and on the webview internal bot.
First upstream failure:
https://luci-milo.appspot.com/buildbot/chromium.perf/Android%20Nexus5X%20Perf/249
With CL range:
http://test-results.appspot.com/revision_range?start=483642&end=483869
Interestingly, also the ref build is failing. Could have been a test runner change?
,
Jul 3 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7fd035e504c5ee5657384c049e203eb7f4c1a384 commit 7fd035e504c5ee5657384c049e203eb7f4c1a384 Author: Juan A. Navarro Perez <perezju@chromium.org> Date: Mon Jul 03 12:09:55 2017 [system health] Disable load:tools:drive on some Android configs Test started recently timing out waiting for login page to load. TBR=nednguyen@google.com Bug: 738854 Change-Id: Id545011a877ddde659c08b89ccfc1cf9527eece2 Reviewed-on: https://chromium-review.googlesource.com/558877 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@{#483991} [modify] https://crrev.com/7fd035e504c5ee5657384c049e203eb7f4c1a384/tools/perf/page_sets/system_health/expectations.py
,
Jul 3 2017
=== Auto-CCing suspected CL author flackr@chromium.org === Hi flackr@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Test failure found with culprit Suspected Commit Author : Robert Flack Commit : 8d097cf30a2dee37de4586de97f06269ed03da09 Date : Fri Jun 30 16:42:01 2017 Subject: Update google_login helper and gmail recordings. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.common_mobile Metric : cpuTimeToFirstMeaningfulPaint_avg/load_tools/load_tools_drive Revision Exit Code N chromium@483641 0 +- N/A 20 good chromium@483698 0 +- N/A 20 good chromium@483727 0 +- N/A 20 good chromium@483731 0 +- N/A 20 good chromium@483732 1 +- N/A 20 bad <-- chromium@483733 1 +- N/A 20 bad chromium@483734 1 +- N/A 20 bad chromium@483741 1 +- N/A 20 bad chromium@483755 1 +- N/A 20 bad chromium@483869 1 +- N/A 20 bad To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.drive system_health.common_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8975096488875290288 For feedback, file a bug with component Speed>Bisection
,
Jul 3 2017
flackr, looks like you also need to update recordings for load:tools:drive
,
Jul 19
From the error it looks like it's independent of the platform and I looked at the flakiness dashboard and Android Nexus5 Perf works fine. Maybe we should try reenabling it? https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=performance_test_suite&tests=system_health.common_mobile%2Fload%3Atools%3Adrive
,
Jul 19
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/15ba1e1ea40000
,
Jul 19
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/15ba1e1ea40000 All of the runs failed. The most common error (1/20 runs) was: IOError: [Errno 2] No such file or directory: '/b/swarming/w/itJvYroK/tmpIJLT8xtelemetry/histograms.json'
,
Jul 23
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16838009a40000
,
Jul 23
📍 Job complete. See results below. https://pinpoint-dot-chromeperf.appspot.com/job/16838009a40000
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
,
Aug 14
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/15a003c4640000
,
Aug 14
Try job builds failed, running another.
,
Aug 15
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16480b04640000
,
Aug 15
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/15a003c4640000 The swarming task expired. The bots are likely overloaded, dead, or misconfigured.
,
Aug 16
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14cb86dc640000
,
Aug 16
📍 Job complete. See results below. https://pinpoint-dot-chromeperf.appspot.com/job/16480b04640000
,
Aug 16
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12a7ca14640000
,
Aug 17
📍 Job complete. See results below. https://pinpoint-dot-chromeperf.appspot.com/job/14cb86dc640000
,
Aug 17
📍 Job complete. See results below. https://pinpoint-dot-chromeperf.appspot.com/job/12a7ca14640000
,
Aug 17
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1396cdca640000
,
Aug 17
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/13dbd3ec640000
,
Aug 17
📍 Job complete. See results below. https://pinpoint-dot-chromeperf.appspot.com/job/13dbd3ec640000
,
Aug 18
📍 Job complete. See results below. https://pinpoint-dot-chromeperf.appspot.com/job/1396cdca640000
,
Aug 20
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/c0893d340eb1c6afb2dfa1ed4a4f42f001451d7f commit c0893d340eb1c6afb2dfa1ed4a4f42f001451d7f Author: Annie Sullivan <sullivan@chromium.org> Date: Mon Aug 20 16:06:40 2018 Re-enable load:tools:drive on Android. Bug: 738854 Change-Id: If29018f3125540bd3abe15f46b5a13994215066b TBR: tdresser@chromium.org Reviewed-on: https://chromium-review.googlesource.com/1174633 Commit-Queue: Annie Sullivan <sullivan@chromium.org> Reviewed-by: Annie Sullivan <sullivan@chromium.org> Cr-Commit-Position: refs/heads/master@{#584463} [modify] https://crrev.com/c0893d340eb1c6afb2dfa1ed4a4f42f001451d7f/tools/perf/expectations.config |
|||
►
Sign in to add a comment |
|||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 3 2017