search

ARMmbed / wifi-ism43362

ISM43362 WiFi driver
17 stars 22 forks source link

mbed-os Greentea tests-network-wifi testsuite fails with AUTH_FAILURE #50

Closed michalpasztamobica closed 5 years ago

michalpasztamobica commented 5 years ago

mbed-os greentea tests-network-wifi is failing on multiple test cases returning AUTH_FAILURE in this line:

[1554349113.14][CONN][RXD] 
[1554349113.14][CONN][RXD] >>> Running case #8: 'WIFI-GET-RSSI'...
[1554349113.24][CONN][INF] found KV pair in stream: {{__testcase_start;WIFI-GET-RSSI}}, queued...
[1554349141.88][CONN][RXD] :36::FAIL: Expected 0 Was -3011
[1554349142.15][CONN][RXD] :40::FAIL: Expected 0 Was -3004
[1554349142.25][CONN][INF] found KV pair in stream: {{__testcase_finish;WIFI-GET-RSSI;0;2}}, queued...
[1554349142.35][CONN][RXD] >>> 'WIFI-GET-RSSI': 0 passed, 2 failed with reason 'Test Cases Failed'
[1554349142.35][CONN][RXD] 
[1554349142.35][CONN][RXD] >>> Running case #9: 'WIFI-CONNECT-PARAMS-VALID-UNSECURE'...
[1554349142.46][CONN][INF] found KV pair in stream: {{__testcase_start;WIFI-CONNECT-PARAMS-VALID-UNSECURE}}, queued...
[1554349170.77][CONN][RXD] :31::FAIL: Expected 0 Was -3011
[1554349170.77][CONN][RXD] :32::FAIL: Expected 0 Was -3004
[1554349192.66][CONN][RXD] :33::FAIL: Expected 0 Was -3011
[1554349192.75][CONN][RXD] :34::FAIL: Expected 0 Was -3004

The issue is 99% reproducible, but I got those tests passing if I commented out the two WIFI-SCAN tests. At first glance I could not find the issue in the code, perhaps a memory corruption somewhere?

This would be in line with the fact that in other test suites, where DISCO simply connects to Wi-Fi AP without scanning, the tests are passing fine.

Another important finding is that these tests only started failing in mbed-os nightly runs two weeks ago. But when I rolled back to mbed-os and ism43326 from before that day I still couldn't pass the wifi suite...

The reason why I decided to file an issue in this project is that we also checked DISCO_F413ZH and it failed in the same way. All other boards connect fine to the Wi-Fi both on our desks and in the RAAS system. Therefore, I would be grateful if you checked this issue.

@TuomoHautamaki , @SeppoTakalo , FYI

jeromecoutant commented 5 years ago

Hi Analysis is on going

michalpasztamobica commented 5 years ago

@jeromecoutant , I am sorry, but I can still see the same AUTH_FAILURE errors in our Greentea test suite, with the latest revision of wifi-ism43362 driver. Would you please double check that the revert which you applied fixes the issue?

michalpasztamobica commented 5 years ago

@jeromecoutant , please, double check. The issue is not fixed. I can see the failures repeated every day in our CI.

jeromecoutant commented 5 years ago

Hi @michalpasztamobica

DISCO_F413ZH seems OK on my side (mbed-os and wifi on master branch)....

target platform_name test suite result elapsed_time (sec) copy_method
DISCO_F413ZH-ARMC6 DISCO_F413ZH tests-network-wifi OK 68.88 default
michalpasztamobica commented 5 years ago

@jeromecoutant , I am sorry, you are right - F413ZH behaves correctly now, so the issues with L475 that we're seeing cannot be related to the wifi driver. We will investigate further on our side. Thanks for checking!