At time of AC disconnected the status is Fully charged.

10/25 23:14:50.614 DEBUG|        base_utils:0280| [stdout] Device: Battery
10/25 23:14:50.614 DEBUG|        base_utils:0280| [stdout]   path:                    /sys/class/power_supply/BAT0
10/25 23:14:50.615 DEBUG|        base_utils:0280| [stdout]   vendor:                  LURUN
10/25 23:14:50.615 DEBUG|        base_utils:0280| [stdout]   model name:              YF2S-06
10/25 23:14:50.615 DEBUG|        base_utils:0280| [stdout]   serial number:           0001
10/25 23:14:50.615 DEBUG|        base_utils:0280| [stdout]   state:                   Fully charged
10/25 23:14:50.616 DEBUG|        base_utils:0280| [stdout]   voltage (V):             8.279
10/25 23:14:50.616 DEBUG|        base_utils:0280| [stdout]   energy (Wh):             37.7104
10/25 23:14:50.616 DEBUG|        base_utils:0280| [stdout]   energy rate (W):         0
10/25 23:14:50.616 DEBUG|        base_utils:0280| [stdout]   current (A):             0
10/25 23:14:50.616 DEBUG|        base_utils:0280| [stdout]   charge (Ah):             5.096
10/25 23:14:50.617 DEBUG|        base_utils:0280| [stdout]   full charge (Ah):        5.096
10/25 23:14:50.617 DEBUG|        base_utils:0280| [stdout]   full charge design (Ah): 5
10/25 23:14:50.617 DEBUG|        base_utils:0280| [stdout]   percentage:              100
10/25 23:14:50.617 DEBUG|        base_utils:0280| [stdout]   display percentage:      100
10/25 23:14:50.617 DEBUG|        base_utils:0280| [stdout]   technology:              Li-ion



This is WAI and test will be changed.

Correction: This is not WAI but proper wait time should be given to discharge or build the charge up for AC adpter after disconnect/connect.

https://chromium-review.googlesource.com/#/c/404530/

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

commit 66d09a26db525782fcf17a49d728d66e45d970a6
Author: Kalin Stoyanov <kalin@chromium.org>
Date: Thu Oct 27 23:56:43 2016

Suspend after RPM switch on or off.

BUG= chromium:660213 
TEST=None

Change-Id: Ibc751e63acf5b0887c5a4df6843d7de292efac6f
Reviewed-on: https://chromium-review.googlesource.com/404530
Commit-Ready: Kalin Stoyanov <kalin@chromium.org>
Tested-by: Kalin Stoyanov <kalin@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>

[modify] https://crrev.com/66d09a26db525782fcf17a49d728d66e45d970a6/server/site_tests/platform_PowerStatusStress/platform_PowerStatusStress.py

Still having this issue on hana M57 and M58

M57: https://wmatrix.googleplex.com/platform/unfiltered?suites=stress,stress2,stress3&days_back=30&releases=57&platforms=hana

M58: https://wmatrix.googleplex.com/platform/unfiltered?suites=stress,stress2,stress3&days_back=30&releases=58&platforms=hana

+kalin, any update on this ?

looks like hana power_supply_info did not return battery info ?
this is from chromeos1-row2-rack1-host2

# power_supply_info 
Device: Line Power
  path:                    /sys/class/power_supply/CROS_USB_PD_CHARGER0
  online:                  yes
  type:                    USB_PD
  enum type:               AC
  voltage (V):             14.848
  current (A):             0
  max voltage (V):         15
  max current (A):         3
  active source:           CROS_USB_PD_CHARGER0
  available sources:       CROS_USB_PD_CHARGER0* [0/0]
  supports dual-role:      yes

Same for chromeos1-row2-rack9-host3. 

The test logs show the missing Device Battery in power_supply_info output and respectively the test does not match the expected values. This is the first iteration at state of discharging.

02/04 00:52:09.797 DEBUG|platform_PowerStat:0071| Resuming...
02/04 00:52:09.798 INFO |             servo:0512| Setting lid_open to yes
02/04 00:52:10.069 DEBUG|          ssh_host:0272| Running (ssh) 'true'
02/04 00:52:13.807 DEBUG|      abstract_ssh:0582| Host chromeos1-row2-rack9-host3 is now up
02/04 00:52:13.808 DEBUG|          ssh_host:0272| Running (ssh) 'power_supply_info'
02/04 00:52:14.512 DEBUG|        base_utils:0280| [stdout] Device: Line Power
02/04 00:52:14.514 DEBUG|        base_utils:0280| [stdout]   path:                    
02/04 00:52:14.514 DEBUG|        base_utils:0280| [stdout]   online:                  yes
02/04 00:52:14.515 DEBUG|        base_utils:0280| [stdout]   type:                    Mains
02/04 00:52:14.515 DEBUG|        base_utils:0280| [stdout]   enum type:               AC
02/04 00:52:14.515 DEBUG|        base_utils:0280| [stdout]   voltage (V):             0
02/04 00:52:14.515 DEBUG|        base_utils:0280| [stdout]   current (A):             0
02/04 00:52:14.516 DEBUG|        base_utils:0280| [stdout]   max voltage (V):         0
02/04 00:52:14.516 DEBUG|        base_utils:0280| [stdout]   max current (A):         0
02/04 00:52:14.516 DEBUG|        base_utils:0280| [stdout]   active source:           
02/04 00:52:14.516 DEBUG|        base_utils:0280| [stdout]   available sources:       
02/04 00:52:14.516 DEBUG|        base_utils:0280| [stdout]   supports dual-role:      yes
02/04 00:52:14.517 ERROR|        base_utils:0280| [stderr] [0204/005213:WARNING:power_supply.cc(676)] Found neither line power nor a battery; assuming that line power is connected
02/04 00:52:14.589 WARNI|              test:0606| Autotest caught exception when running test:
Traceback (most recent call last):
  File "/usr/local/autotest/client/common_lib/test.py", line 600, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 804, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 461, in execute
    dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 347, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 376, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/server/site_tests/platform_PowerStatusStress/platform_PowerStatusStress.py", line 154, in run_once
    self.switch_power_and_verify(False, expected)
  File "/usr/local/autotest/server/site_tests/platform_PowerStatusStress/platform_PowerStatusStress.py", line 118, in switch_power_and_verify
    raise error.TestFail('Bad %s state!' % bat_state)
TestFail: Bad DISCHARGING state!

looks like we have old FW on the lab device, after update the test now passes.

Awesome. Thanks!

This issue has disappeared with the firmware version 
fwid                   = Google_Hana.8438.60.0          # Active firmware ID
ro_fwid                = Google_Hana.8438.60.0          # Read-only firmware ID

on chromeos1-row2-rack1-host6

chromeos1-row2-rack10-host3 and chromeos1-row2-rack9-host3 also have started passing latterly.

https://wmatrix.googleplex.com/platform/unfiltered?suites=stress%2Cstress2%2Cstress3&days_back=30&releases=58&platforms=hana

https://wmatrix.googleplex.com/platform/unfiltered?suites=stress%2Cstress2%2Cstress3&days_back=30&releases=57&platforms=hana