Failed build:
https://uberchromegw.corp.google.com/i/chromeos/builders/whirlwind-paladin/builds/10334
jetstream_NetworkInterfaces
01/04 16:03:50.880 DEBUG| autotest:1310| AUTOTEST_STATUS:: FAIL jetstream_NetworkInterfaces jetstream_NetworkInterfaces timestamp=1515031884 localtime=Jan 04 02:11:24 Timed out waiting for AP to appear operational
01/04 16:03:50.880 INFO | server_job:0218| FAIL jetstream_NetworkInterfaces jetstream_NetworkInterfaces timestamp=1515031884 localtime=Jan 03 18:11:24 Timed out waiting for AP to appear operational
01/04 16:03:50.881 INFO | server_job:1401| Parsing lines in fast mode
01/04 16:03:50.881 ERROR| logging_manager:0626| tko parser: update RUNNING reason: Timed out waiting for AP to appear operational
From DUT log:
01/04 02:10:21.552 DEBUG| utils:0212| Running 'ip addr show wlan-2400mhz 2> /dev/null'
01/04 02:10:21.590 DEBUG| utils:0280| [stdout] 11: wlan-2400mhz: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
01/04 02:10:21.593 DEBUG| utils:0280| [stdout] link/ether 60:e3:27:69:2a:47 brd ff:ff:ff:ff:ff:ff
01/04 02:10:21.597 DEBUG| utils:0212| Running 'ip addr show wlan-5000mhz 2> /dev/null'
01/04 02:10:21.633 DEBUG| utils:0280| [stdout] 12: wlan-5000mhz: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
01/04 02:10:21.636 DEBUG| utils:0280| [stdout] link/ether 60:e3:27:69:52:ee brd ff:ff:ff:ff:ff:ff
both wlan ip addr are DOWN, they should be UP in the passed cases.
Not triaged yet, it could be failed by commit or test/infra flake.
Comment 1 by jrbarnette@chromium.org
, Jan 5 2018Status: Duplicate (was: Untriaged)