New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 604793 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

power_LoadTest fails confusingly on chromeboxes

Project Member Reported by jdufault@chromium.org, Apr 19 2016

Issue description

Example failure is at [1]. All runs at [2].

Stack trace:

  Traceback (most recent call last):
    File "/usr/local/autotest/common_lib/test.py", line 567, in _exec
      _cherry_pick_call(self.initialize, *args, **dargs)
    File "/usr/local/autotest/common_lib/test.py", line 719, in _cherry_pick_call
      return func(*p_args, **p_dargs)
    File "/usr/local/autotest/tests/power_LoadTest/power_LoadTest.py", line 200, in initialize
      self._ah_charge_start = self._power_status.battery[0].charge_now
  TypeError: 'NoneType' object has no attribute '__getitem__'

Seems to me that the battery value on self._power_status is None. Looking at SysStat in power_status.py, this happens when there is no battery path (there is no battery?).

What does this indicate? Can the logs here be better, ie, is the test failing because there is no battery?

1: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/60472111-chromeos-test/chromeos4-row2-rack5-host8/power_LoadTest/
2: https://wmatrix.googleplex.com/unfiltered?hide_missing=True&releases=tot&tests=power_LoadTest


 

Comment 1 by tbroch@chromium.org, Apr 19 2016

Components: OS>Kernel>Power
Status: Assigned (was: Untriaged)
Summary: power_LoadTest fails confusingly on chromeboxes (was: power_LoadStatus fails confusingly)
Yes this failure is due to runing on zako which doesn't have a battery.  We should make this clearer on chromeboxes for any/all power_* autotests.

I'll have a look.

Comment 2 by tbroch@chromium.org, Apr 20 2016

Status: Started (was: Assigned)
Project Member

Comment 3 by bugdroid1@chromium.org, Apr 21 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/4d4f45772fd8e708e019e31fc41f0cfa9d764919

commit 4d4f45772fd8e708e019e31fc41f0cfa9d764919
Author: Todd Broch <tbroch@chromium.org>
Date: Wed Apr 20 22:47:07 2016

power_LoadTest: skip test for devices without batteries.

BUG= chromium:604793 
TEST=run on test on chromebox and see if fail w/
  TestNAError: Device designed without battery. Skipping test.

Change-Id: I7d92b6a8bbf661a9500d2790a9380a31804208ea
Reviewed-on: https://chromium-review.googlesource.com/340001
Commit-Ready: Todd Broch <tbroch@chromium.org>
Tested-by: Todd Broch <tbroch@chromium.org>
Reviewed-by: Sameer Nanda <snanda@chromium.org>

[modify] https://crrev.com/4d4f45772fd8e708e019e31fc41f0cfa9d764919/client/site_tests/power_LoadTest/power_LoadTest.py

Comment 4 by russ.s...@intel.com, Apr 21 2016

I continually get a failure on power_LoadTest with the message: "Unhandled AttributeError: 'URLError' object has no attribute 'msg'". This happens on cyan, chell and lars. Sometimes I can work around by rebooting the DUT and exiting/re-entering the chroot. But lately that is not working. We rely on this autotest for weekly battery life testing so it is a high priority item. Please fix this as we need it for SKL products.

Comment 5 by tbroch@chromium.org, Apr 22 2016

Status: Verified (was: Started)
fix in #c3 should be in build >= R52-8222.0.0 and I can see is functioning from latest wmatrix runs,

https://wmatrix.googleplex.com/unfiltered?platforms=panther,zako&releases=52&tests=power_LoadTest


For issue in #c4 lets track in a separate issue.  I see similar error signature here: crbug.com/555383.

Please add logs / detail there if you agree its the same and I'll re-open and pursue further.

Sign in to add a comment