Feature/fix wifi testing #232
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In a loud enterprise wifi environment 30 seconds isn't always enough to find, connect and setup the wifi stack, then also test.
This allows us to print the full IP info actually used during wifi testing, to quickly see any potential issues with the IP stack.
This is so we leave the now extended test enough time to fail after 60 seconds before cutting it off from the calling bash script.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Minor timeout tweaks to improve our chances of establishing a Wifi connection in a noisy signal environment and a function to provide us with some basic diagnostic IP information. Coupled together with work done moving our Lab AP antenna, this should keep things stable for now.