New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 712766 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

[wifi_release][VeyronTiger][Fievel] network_WiFi_SimpleConnect failing with "Association timed out" error.

Project Member Reported by aashuto...@chromium.org, Apr 18 2017

Issue description

The following tests are failing only for Veyron Tiger and Fievel devices,

network_WiFi_SimpleConnect.wifi_checkWPA_multi  network_WiFi_SimpleConnect.wifi_checkWPA_CCMP  network_WiFi_SimpleConnect.wifi_checkRawPMK network_WiFi_SimpleConnect.wifi_check1x_PEAP network_WiFi_SimpleConnect.wifi_checkWPA_TKIP network_WiFi_SimpleConnect.wifi_checkOddWPAPassphrases network_WiFi_SimpleConnect.wifi_check1x_WPA  network_WiFi_SimpleConnect.wifi_check1x_TTLS

Sample Error 

Traceback (most recent call last):
  File "/tmp/veyron-tiger_9202.71.0_stable_Autotest/chromeos-hwqual-veyron_tiger-R57-9202.71.0/autotest/client/common_lib/test.py", line 600, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/tmp/veyron-tiger_9202.71.0_stable_Autotest/chromeos-hwqual-veyron_tiger-R57-9202.71.0/autotest/client/common_lib/test.py", line 804, in _call_test_function
    return func(*args, **dargs)
  File "/tmp/veyron-tiger_9202.71.0_stable_Autotest/chromeos-hwqual-veyron_tiger-R57-9202.71.0/autotest/client/common_lib/test.py", line 461, in execute
    dargs)
  File "/tmp/veyron-tiger_9202.71.0_stable_Autotest/chromeos-hwqual-veyron_tiger-R57-9202.71.0/autotest/client/common_lib/test.py", line 347, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/tmp/veyron-tiger_9202.71.0_stable_Autotest/chromeos-hwqual-veyron_tiger-R57-9202.71.0/autotest/client/common_lib/test.py", line 376, in _call_run_once
    self.run_once(*args, **dargs)
  File "/tmp/veyron-tiger_9202.71.0_stable_Autotest/chromeos-hwqual-veyron_tiger-R57-9202.71.0/autotest/server/site_tests/network_WiFi_SimpleConnect/network_WiFi_SimpleConnect.py", line 61, in run_once
    raise e
TestFail: Expected connection to SimpleConnect_d_ev3hy_ch1 to succeed, but it failed with reason: FAIL(Association timed out).

Device Info for Fievel and Tiger:
	
Based on: Pinky/Elmyra	
Processor: Rockchip 	
Kernel: 3.14 
Wifi: Marvell 8897	
				
Logs attached. 	
 
test_that_results_fievel.tar.gz
2.7 MB Download
Cc: keta...@chromium.org rjahagir@chromium.org
+TPM +Morning planner

This was found during the FSI testing of fievel yesterday :
https://cros-goldeneye.corp.google.com/chromeos/console/qaRelease?releaseName=M57-STABLE-CHROMEOS-4-FievelOnly
Labels: -Pri-2 Pri-1
Is this new in .71 or did this fail in prior builds as well?

I don't see anything wifi related between the passing tiger build and fievel here https://crosland.corp.google.com/log/9202.64.0..9202.71.0

Is there any chance these are flaky WiFi tests?
Cc: bhthompson@google.com

Comment 5 by dchan@google.com, Apr 18 2017

Cc: alexpau@chromium.org
The above WiFi test are consistently failing. This was earlier ignored (I saw similar failure for Tiger) as device with similar chipset and kernel version like veyron_jaq, jerry,mighty didn't see this issue. Also, we don't have a Fievel chromebox in wificell for testing. 

https://wmatrix.googleplex.com/unfiltered?suites=wifi_release&releases=57&days_back=30&platforms=veyron_jerry,veyron_jaq,veyron_mighty

Was the test failing in the prior build for these systems?

We need to get an idea of if this is really a regression, and how much it matters.

Kirtika, Kevin, do you have input on this one?
Agree with figuring out whether this is a regression or if it was always broken on this setup.

There was talk of updating the wifi_cell images a few weeks ago.  Did we ever change anything on that end?  Last I heard they were running an image that was several years old, because it was put together by hand.

We also took a bunch of wpa_supplicant commits around 4/1, mostly from upstream.

Comment 9 by josa...@google.com, Apr 19 2017

Owner: kirtika@chromium.org
Any update on this case?
Kirtika, are you the right owner for this?
Status: Assigned (was: Untriaged)

Sign in to add a comment