-
Notifications
You must be signed in to change notification settings - Fork 3k
Mbedgt netsocket tc fixes #8235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
2.4GHz and 5GHz channels might be using the same SSID. Wifi scan might also fail occasionally to find secure- and unsecure channels on same scan so lets not assume that we'll find both.
@SeppoTakalo, @KariHaapalehto please check. @kivaisan, @AriParkkila for your information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test plan is in the same repo, so fix that as well.
@SeppoTakalo test specification updated. |
@0xc0170 needs:CI |
@0xc0170 would you please start the build. |
There's 5.10.1 release candidate that will be retriggered in few minutes, once that is in, we will start this one |
/morph build |
Build : SUCCESSBuild number : 3216 Triggering tests/morph test |
Test : SUCCESSBuild number : 3018 |
@0xc0170 problems with exporter-build? |
/morph export-build |
Exporter Build : SUCCESSBuild number : 2896 |
Description
Allows usage of port zero as destination on mbedgt-netsocket test cases.
Drops channel number check from mbedgt-network-wifi test cases because 2.4GHz channels and 5GHz channels might share same SSID.
Wifi scan might not reveal both SSIDs - unsecure and secure - at same run so we are happy if one of those is found.
Pull request type