system_health.memory_mobile timing out |
|||
Issue descriptionAfter setting the pageset_repeat=3 for memory metrics, the test is now being timed out and no data is uploaded to dashboards. Error reporting is not great, but we do see e.g. on the "Sharded Perf Tests" step: I 9457.563s device_shard_helper(0) system_health.memory_mobile.reference : exit_code=-1 in 3600 secs on device 03848d7af0e9447d https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%281%29/builds/4430/steps/Sharded%20Perf%20Tests/logs/stdio Not sure what is the best course of action here. Lift the default timeout to ~3 hours on all tests? Or do some special-casing for system health?
,
Oct 14 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/clank/internal/apps/+/af14273c5dd43e0cedb7a875c79452d5219bb348 commit af14273c5dd43e0cedb7a875c79452d5219bb348 Author: Juan A. Navarro Perez <perezju@google.com> Date: Fri Oct 14 12:14:27 2016
,
Oct 14 2016
That patch is to increase the timeout to 3 hours on downstream bots. We would still need to figure out something for upstream.
,
Oct 14 2016
For upstream, I think we can just default timeout to 3 hours (still kill the test if stdout is silent for too long). Currently, the new loading benchmark is also hit the timeout limit: issue 655648
,
Oct 14 2016
,
Oct 14 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/c7f66928a50ec3a5751c245764f9872b7c494262 commit c7f66928a50ec3a5751c245764f9872b7c494262 Author: perezju <perezju@chromium.org> Date: Fri Oct 14 21:59:17 2016 [build/android] Increase timeout of perf tests to 3 hours Some tests are now timing out because they take longer to run. BUG= 655965 , 655648 Review-Url: https://codereview.chromium.org/2423443002 Cr-Commit-Position: refs/heads/master@{#425483} [modify] https://crrev.com/c7f66928a50ec3a5751c245764f9872b7c494262/build/android/pylib/local/device/local_device_perf_test_run.py
,
Oct 17 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by perezju@chromium.org
, Oct 14 2016