telemetry_AFDOGenearte timed-out again |
||||
Issue descriptionThe time needed to complete a run increased 50% - 70%. https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/78122773-chromeos-test/chromeos2-row3-rack9-host16/debug/ 09/26 00:33:12.338 INFO |telemetry_AFDOGene:0196| Completed Telemetry benchmark page_cycler_v2.typical_25 in 1603.006909 seconds 09/26 00:55:25.685 INFO |telemetry_AFDOGene:0196| Completed Telemetry benchmark page_cycler_v2.intl_ja_zh in 1333.343482 seconds 09/26 01:06:51.650 INFO |telemetry_AFDOGene:0196| Completed Telemetry benchmark page_cycler_v2.intl_ar_fa_he in 685.964527 seconds
,
Sep 26 2016
,
Sep 27 2016
Previous successful run in the lab: 09/25 19:52:01.271 INFO |telemetry_AFDOGene:0196| Completed Telemetry benchmark page_cycler_v2.typical_25 in 899.829730 seconds 09/25 20:08:06.361 INFO |telemetry_AFDOGene:0196| Completed Telemetry benchmark page_cycler_v2.intl_ja_zh in 965.089726 seconds 09/25 20:16:25.343 INFO |telemetry_AFDOGene:0196| Completed Telemetry benchmark page_cycler_v2.intl_ar_fa_he in 498.980650 seconds Not sure if it's related to the lab or not, but it's even faster when running locally. Image on the dut and scripts running on my workstation are up-to-date. 18:50:25 INFO | autoserv| Completed Telemetry benchmark page_cycler_v2.typical_25 in 543.974196 seconds 19:02:55 INFO | autoserv| Completed Telemetry benchmark page_cycler_v2.intl_ja_zh in 749.402352 seconds 19:09:09 INFO | autoserv| Completed Telemetry benchmark page_cycler_v2.intl_ar_fa_he in 374.046839 seconds I saw all the lumpys in cautotest/ are labeled with "power:battery" so I'm trying to run the test again with battery power to see if that can be reproduced.
,
Sep 27 2016
There is no difference between AC and batter power.
,
Oct 1 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/5dadd23214632db04b6421ff8506ab68094c56bb commit 5dadd23214632db04b6421ff8506ab68094c56bb Author: Ting-Yuan Huang <laszio@chromium.org> Date: Tue Sep 27 00:37:09 2016 AFDOGenerate: Increase the timeout to 100 mins. This is a temporary solution that the test is taking longer and longer. TEST=none BUG= chromium:650331 Change-Id: Ie922c392c96726d9cdb54e2a948b1643f8e5bd86 Reviewed-on: https://chromium-review.googlesource.com/389872 Commit-Ready: Ting-Yuan Huang <laszio@chromium.org> Tested-by: Ting-Yuan Huang <laszio@chromium.org> Reviewed-by: Luis Lozano <llozano@chromium.org> [modify] https://crrev.com/5dadd23214632db04b6421ff8506ab68094c56bb/cbuildbot/config_dump.json [modify] https://crrev.com/5dadd23214632db04b6421ff8506ab68094c56bb/cbuildbot/constants.py
,
Feb 23 2017
can this bug be closed?
,
Feb 23 2017
OK. I don't know why but page_cycler_v2.typical_25 finishes in 19mins on chell recently. |
||||
►
Sign in to add a comment |
||||
Comment 1 by nedngu...@google.com
, Sep 26 2016