samus: re-enable lucid sleep (v1) functionality. |
|||||||||
Issue descriptionBug to track re-enabling lucid sleep on samus. Plan is to run suite:wificell_lucidsleep power_DarkResumeDisplay autotests and if successful re-enable.
,
Jun 8 2016
With patch applied from #c1 network_WiFi_DarkResumeActiveScans is passing. ------------------------------------------------------------------------------------------------------------------------ /tmp/test_that_results_gPjilQ/results-1-network_WiFi_DarkResumeActiveScans [ PASSED ] /tmp/test_that_results_gPjilQ/results-1-network_WiFi_DarkResumeActiveScans/network_WiFi_DarkResumeActiveScans [ PASSED ] ------------------------------------------------------------------------------------------------------------------------- power_DarkResumeDisplay however fails, /tmp/test_that_results_P85H6l/results-1-power_DarkResumeDisplay [ FAILED ] /tmp/test_that_results_P85H6l/results-1-power_DarkResumeDisplay FAIL: Unhandled AttributeError: 'NoneType' object has no attribute 'ctrl_key' /tmp/test_that_results_P85H6l/results-1-power_DarkResumeDisplay/power_DarkResumeDisplay [ FAILED ] /tmp/test_that_results_P85H6l/results-1-power_DarkResumeDisplay/power_DarkResumeDisplay FAIL: Unhandled AttributeError: 'NoneType' object has no attribute 'ctrl_key'
,
Jun 8 2016
ctrl_key is an attribute of the servo, so if you are seeing this failure your DUT likely doesn't have a servo attached.
,
Jun 9 2016
Servo is there ... test needs to parse the args in the case its not localhost. Fix coming.
,
Jun 9 2016
Passed with change to account for remote servo (CL https://chromium-review.googlesource.com/351230) /tmp/test_that_results_X79o7x/results-1-power_DarkResumeDisplay [ PASSED ] /tmp/test_that_results_X79o7x/results-1-power_DarkResumeDisplay/power_DarkResumeDisplay [ PASSED ] Failing power_DarkResumeShutdownServer however with, /tmp/test_that_results_OusbGE/results-1-power_DarkResumeShutdownServer.power_manual/power_DarkResumeShutdownServer [ FAILED ] /tmp/test_that_results_OusbGE/results-1-power_DarkResumeShutdownServer.power_manual/power_DarkResumeShutdownServer FAIL: DUT did not turn back on after shutting down
,
Jun 9 2016
We might have to wait for the DUT to power down completely in the power_DarkResumeShutdownServer test. The system_ColdBoot test does this.
,
Jun 10 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/2ba796de96511cc467afbd94921055bb1a78614e commit 2ba796de96511cc467afbd94921055bb1a78614e Author: Todd Broch <tbroch@chromium.org> Date: Thu Jun 09 16:40:52 2016 power_DarkResumeDisplay: parse command line servo args. BUG= chromium:618413 TEST=manual test_that $cut power_DarkResumeDisplay \ --args "servo_host:${servo} servo_port:9999" No longer see exception, 'NoneType' object has no attribute 'ctrl_key' Change-Id: I83c8e0485a1d2315afa6bda7a33eb9e944aa1650 Reviewed-on: https://chromium-review.googlesource.com/351230 Commit-Ready: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> Reviewed-by: Eric Caruso <ejcaruso@chromium.org> [modify] https://crrev.com/2ba796de96511cc467afbd94921055bb1a78614e/server/site_tests/power_DarkResumeDisplay/control
,
Jun 14 2016
Fix for power_DarkResumeShutdownServer to allow different power_methods works for 'servoj10' + 'ECO strip 2.0' connected to servo V3 once I refactor reboot stuff to match Derek's suggestion in #c6. Unfortunately more recent image (built 6/9) fails ~1/2 of wifi_lucidsleep suite now: /tmp/test_that_results_jK_duB/results-01-network_WiFi_ReconnectInDarkResume.Stress [ FAILED ] /tmp/test_that_results_jK_duB/results-01-network_WiFi_ReconnectInDarkResume.Stress FAIL: Client only came up in 0 dark resumes during the test (expected: at least 10) /tmp/test_that_results_jK_duB/results-01-network_WiFi_ReconnectInDarkResume.Stress/network_WiFi_ReconnectInDarkResume.Stress [ FAILED ] /tmp/test_that_results_jK_duB/results-01-network_WiFi_ReconnectInDarkResume.Stress/network_WiFi_ReconnectInDarkResume.Stress FAIL: Client only came up in 0 dark resumes during the test (expected: at least 10) /tmp/test_that_results_jK_duB/results-02-network_WiFi_DarkResumeActiveScans [ FAILED ] /tmp/test_that_results_jK_duB/results-02-network_WiFi_DarkResumeActiveScans FAIL: Client failed to wake on packet. /tmp/test_that_results_jK_duB/results-02-network_WiFi_DarkResumeActiveScans/network_WiFi_DarkResumeActiveScans [ FAILED ] /tmp/test_that_results_jK_duB/results-02-network_WiFi_DarkResumeActiveScans/network_WiFi_DarkResumeActiveScans FAIL: Client failed to wake on packet. /tmp/test_that_results_jK_duB/results-03-network_WiFi_WakeOnSSID [ PASSED ] /tmp/test_that_results_jK_duB/results-03-network_WiFi_WakeOnSSID/network_WiFi_WakeOnSSID [ PASSED ] /tmp/test_that_results_jK_duB/results-04-network_WiFi_ReconnectInDarkResume.DisconnectBeforeSuspendDiffAP [ PASSED ] /tmp/test_that_results_jK_duB/results-04-network_WiFi_ReconnectInDarkResume.DisconnectBeforeSuspendDiffAP/network_WiFi_ReconnectInDarkResume.DisconnectBeforeSuspendDiffAP [ PASSED ] /tmp/test_that_results_jK_duB/results-05-network_WiFi_FastReconnectInDarkResume [ FAILED ] /tmp/test_that_results_jK_duB/results-05-network_WiFi_FastReconnectInDarkResume FAIL: Expected exactly one dark resume /tmp/test_that_results_jK_duB/results-05-network_WiFi_FastReconnectInDarkResume/network_WiFi_FastReconnectInDarkResume [ FAILED ] /tmp/test_that_results_jK_duB/results-05-network_WiFi_FastReconnectInDarkResume/network_WiFi_FastReconnectInDarkResume FAIL: Expected exactly one dark resume /tmp/test_that_results_jK_duB/results-06-network_WiFi_ReconnectInDarkResume.DisconnectAfterSuspendSameAP [ FAILED ] /tmp/test_that_results_jK_duB/results-06-network_WiFi_ReconnectInDarkResume.DisconnectAfterSuspendSameAP FAIL: Client only came up in 0 dark resumes during the test (expected: at least 2) /tmp/test_that_results_jK_duB/results-06-network_WiFi_ReconnectInDarkResume.DisconnectAfterSuspendSameAP/network_WiFi_ReconnectInDarkResume.DisconnectAfterSuspendSameAP [ FAILED ] /tmp/test_that_results_jK_duB/results-06-network_WiFi_ReconnectInDarkResume.DisconnectAfterSuspendSameAP/network_WiFi_ReconnectInDarkResume.DisconnectAfterSuspendSameAP FAIL: Client only came up in 0 dark resumes during the test (expected: at least 2) /tmp/test_that_results_jK_duB/results-07-network_WiFi_WoWLAN [ FAILED ] /tmp/test_that_results_jK_duB/results-07-network_WiFi_WoWLAN FAIL: Client woke up fully. /tmp/test_that_results_jK_duB/results-07-network_WiFi_WoWLAN/network_WiFi_WoWLAN [ FAILED ] /tmp/test_that_results_jK_duB/results-07-network_WiFi_WoWLAN/network_WiFi_WoWLAN FAIL: Client woke up fully. /tmp/test_that_results_jK_duB/results-08-network_WiFi_ReconnectInDarkResume.DisconnectAfterSuspendDiffAP [ FAILED ] /tmp/test_that_results_jK_duB/results-08-network_WiFi_ReconnectInDarkResume.DisconnectAfterSuspendDiffAP FAIL: Client only came up in 0 dark resumes during the test (expected: at least 2) /tmp/test_that_results_jK_duB/results-08-network_WiFi_ReconnectInDarkResume.DisconnectAfterSuspendDiffAP/network_WiFi_ReconnectInDarkResume.DisconnectAfterSuspendDiffAP [ FAILED ] /tmp/test_that_results_jK_duB/results-08-network_WiFi_ReconnectInDarkResume.DisconnectAfterSuspendDiffAP/network_WiFi_ReconnectInDarkResume.DisconnectAfterSuspendDiffAP FAIL: Client only came up in 0 dark resumes during the test (expected: at least 2) /tmp/test_that_results_jK_duB/results-09-network_WiFi_WakeOnDisconnect [ FAILED ] /tmp/test_that_results_jK_duB/results-09-network_WiFi_WakeOnDisconnect FAIL: Client woke up fully. /tmp/test_that_results_jK_duB/results-09-network_WiFi_WakeOnDisconnect/network_WiFi_WakeOnDisconnect [ FAILED ] /tmp/test_that_results_jK_duB/results-09-network_WiFi_WakeOnDisconnect/network_WiFi_WakeOnDisconnect FAIL: Client woke up fully. /tmp/test_that_results_jK_duB/results-10-network_WiFi_WakeOnWiFiThrottling [ FAILED ] /tmp/test_that_results_jK_duB/results-10-network_WiFi_WakeOnWiFiThrottling FAIL: Client did not enter the expected number of dark resumes (actual: 0, expected: 3) /tmp/test_that_results_jK_duB/results-10-network_WiFi_WakeOnWiFiThrottling/network_WiFi_WakeOnWiFiThrottling [ FAILED ] /tmp/test_that_results_jK_duB/results-10-network_WiFi_WakeOnWiFiThrottling/network_WiFi_WakeOnWiFiThrottling FAIL: Client did not enter the expected number of dark resumes (actual: 0, expected: 3) /tmp/test_that_results_jK_duB/results-11-network_WiFi_ReconnectInDarkResume.DisconnectBeforeSuspendSameAP [ PASSED ] /tmp/test_that_results_jK_duB/results-11-network_WiFi_ReconnectInDarkResume.DisconnectBeforeSuspendSameAP/network_WiFi_ReconnectInDarkResume.DisconnectBeforeSuspendSameAP [ PASSED ]
,
Jun 14 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/fb4b01bfeaea7833d4cccdb2c0b76cd68fcb2558 commit fb4b01bfeaea7833d4cccdb2c0b76cd68fcb2558 Author: Todd Broch <tbroch@chromium.org> Date: Thu Jun 09 21:16:24 2016 power_DarkResumeShutdownServer: allow different power_method. For testing at desk allow 'power_method' to be set via control file. BUG= chromium:618413 TEST=create a control file with power_method='manual' and run test. See prompts like, 16:05:20 INFO | autoserv| You have 10 seconds to set the AC power to ON. 16:05:40 INFO | autoserv| You have 10 seconds to set the AC power to OFF. Change-Id: I78be3f702de9691850c7f64d864b0d20113f1163 Reviewed-on: https://chromium-review.googlesource.com/351343 Commit-Ready: Todd Broch <tbroch@chromium.org> Tested-by: Todd Broch <tbroch@chromium.org> Reviewed-by: Derek Basehore <dbasehore@chromium.org> [modify] https://crrev.com/fb4b01bfeaea7833d4cccdb2c0b76cd68fcb2558/server/site_tests/power_DarkResumeShutdownServer/power_DarkResumeShutdownServer.py
,
Jul 6 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 21 2016
,
Feb 17 2017
,
Feb 23 2017
,
Feb 23 2017
Testing effort and bugs to re-enable this feature make it a wontfix for this platform for the foreseeable future. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by tbroch@chromium.org
, Jun 8 2016Got first run on my suite:wifi_lucidsleep with wificell via, test_that wificell-dut network_WiFi_WakeOnSSID --args "servo_host:${bb} servo_port:9999" Small snag (fix here: https://chromium-review.googlesource.com/#/c/349404/) for /tmp/test_that_results_yRoj6b/results-02-network_WiFi_DarkResumeActiveScans [ FAILED ] /tmp/test_that_results_yRoj6b/results-02-network_WiFi_DarkResumeActiveScans FAIL: Unhandled AttributeError: 'module' object has no attribute 'poll_for_condition' /tmp/test_that_results_yRoj6b/results-02-network_WiFi_DarkResumeActiveScans/network_WiFi_DarkResumeActiveScans [ FAILED ] /tmp/test_that_results_yRoj6b/results-02-network_WiFi_DarkResumeActiveScans/network_WiFi_DarkResumeActiveScans FAIL: Unhandled AttributeError: 'module' object has no attribute 'poll_for_condition' Rest of the tests passed (see test_report.log attached) Test takes ~50min on a single host.