CHAOS LAB: Fix chaos issues and get wifi tests to run as expected |
||||||||||||||||||||||||
Issue description
Chaos tests have been failing due to the following trace for some time.
Traceback (most recent call last):
File "/usr/local/autotest/server/cros/ap_configurators/ap_cartridge.py", line 52, in _apply_settings
configurator.apply_settings()
File "/usr/local/autotest/server/cros/ap_configurators/dynamic_ap_configurator.py", line 771, in apply_settings
self.establish_driver_connection()
File "/usr/local/autotest/server/cros/ap_configurators/dynamic_ap_configurator.py", line 723, in establish_driver_connection
self._webdriver_port)
File "/usr/local/autotest/server/cros/ap_configurators/dynamic_ap_configurator.py", line 268, in check_webdriver_ready
raise error.TestError(err)
TestError: ('Could not establish connection: %s', 'localhost')
This bug will used to track all chaos related fixes until that lab is up and running tests on regular basis.
⛆ |
|
|
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 7 2017
,
Dec 9 2017
,
Apr 25 2018
Closing all Choas lab bugs as we are moving away from dynamic configuration of the APs. These APs have all been reset and FW updated as needed. We have also split the APs equally across 3 RF chambers where they will be manually configured (1 time) to specified configurations. |
|||||||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||||||||||
Comment 1 by bugdroid1@chromium.org
, Nov 16 2017