Issue metadata
Sign in to add a comment
|
power.idle_platform failing on chromium.perf/Mac Air 10.11 Perf |
||||||||||||||||||||||
Issue descriptionpower.idle_platform failing on chromium.perf/Mac Air 10.11 Perf Builders failed on: - Mac Air 10.11 Perf: https://build.chromium.org/p/chromium.perf/builders/Mac%20Air%2010.11%20Perf https://chromium-swarm.appspot.com/task?id=36eebaed56981410&refresh=10&show_raw=1 is the relevant task. Looks like communication to the battor broke.
,
Jun 24 2017
For subprocess timeout, we should use https://cs.chromium.org/chromium/infra/luci/client/utils/subprocess42.py?q=process42&dr=C&l=5
,
Jun 26 2017
Is the job timing out? I'm seeing the whole task took something like 2m30s. Am I looking at the wrong thing?
,
Jun 26 2017
I think what's going on here is a test failure and not a timed out
,
Jun 26 2017
2m30s counting run time and processing time for the benchmarks seems reasonable. It is not timing out. The communication with the BattOr fails during the 120s test. This might be fixed with the new firmware: https://codereview.chromium.org/2956903002/
,
Jun 27 2017
I'm going to postpone looking at this bug for a day until we have more data points after the new firmware that Randy released yesterday.
,
Jun 28 2017
I'm gonna go ahead and close this. I think this is just a manifestation of some other timeout issues that we're seeing with the BattOrs, and it looks like the power.idle_platform timeout actually worked as expected (only taking 2m30s to run). |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by rnep...@chromium.org
, Jun 24 2017