graphics_PowerConsumption failing on many boards in the lab |
||||
Issue descriptionhttps://stainless.corp.google.com/search?view=list&first_date=2018-07-10&last_date=2018-07-12&test=graphics_PowerConsumption&status=WARN&status=FAIL&status=ERROR&status=ALERT&exclude_cts=true&exclude_not_run=false&exclude_non_release=true&exclude_au=true&exclude_acts=true&exclude_retried=true&exclude_non_production=false Stainless shows widespread failures with reason: Unhandled RemotePowerException: Client call exception: <Fault 1: "<class 'autotest_lib.site_utils.rpm_control_system.rpm_infrastructure_exception.RPMInfrastructureException'>:Can not retrieve complete rpm informationfrom AFE for chromeos4-row8-rack4-host1, please make sure powerunit_hostname and powerunit_outlet are in the host's attributes."> Some are failing with: Unhandled RemotePowerException: Failed to change outlet status for host: chromeos2-row2-rack11-host15 to state: ON. Occasionally: Unhandled RemotePowerException: Client call exception: <Fault 1: "<type 'exceptions.AttributeError'>:'NoneType' object has no attribute 'queue_request'"> And some with: Unhandled AutoservSSHTimeout: ('ssh timed out', * Command: Some boards are flaky, but some consistently fail: astronaut buddy daisy_skate gnawty grunt heli pantheon scarlet sona vayne ihf, any global ideas before digging deeper?
,
Jul 13
+folks from power land.
,
Jul 17
b/111524648 should address powerunit_* issue b/111524203 should address to state: ON issue b/111525179 should address ssh timeout issue due to device's battery permanent failure For example, chromeos4-row9-rack1-host11 ssh_lab root@chromeos4-row9-rack1-host11.cros power_supply_info Warning: Permanently added 'chromeos4-row9-rack1-host11.cros.corp.google.com,100.115.200.6' (ED25519) to the list of known hosts. Device: Line Power path: /sys/class/power_supply/AC online: yes type: Mains enum type: AC voltage (V): unknown current (A): unknown max voltage (V): 0 max current (A): 0 active source: AC available sources: AC* [/] supports dual-role: no
,
Jul 20
Looks like most of the current failures are now a result of b/111524203 I'll plan to monitor the lab fixes and close once things look green again.
,
Nov 6
,
Nov 13
In general test is now passing on many runs. Current failures seem to be related to one-off RPM issues. chromeos2-row8-rack5-host9, please make sure powerunit_hostname and powerunit_outlet are in the host's attributes."">" chromeos6-row6-rack4-host11, please make sure powerunit_hostname and powerunit_outlet are in the host's attributes."">" chromeos6-row4-rack23-host21, please make sure powerunit_hostname and powerunit_outlet are in the host's attributes."">" chromeos4-row10-rack3-host13, please make sure powerunit_hostname and powerunit_outlet are in the host's attributes."">" chromeos6-row2-rack6-host4, please make sure powerunit_hostname and powerunit_outlet are in the host's attributes."">" chromeos6-row6-rack24-host10, please make sure powerunit_hostname and powerunit_outlet are in the host's attributes."">" chromeos4-row10-rack11-host3, please make sure powerunit_hostname and powerunit_outlet are in the host's attributes."">" chromeos6-row6-rack9-host4, please make sure powerunit_hostname and powerunit_outlet are in the host's attributes."">" chromeos6-row19-rack15-host7 to state: ON." Will file separate lab fix request for those.
,
Nov 13
b/119443142 for hosts mentioned in #6 |
||||
►
Sign in to add a comment |
||||
Comment 1 by ihf@chromium.org
, Jul 12Labels: OS-Chrome