connectivity tests: avoid HardFault with null pointer #15068
Merged
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.
Summary of changes
Issue occurs with wrong mbed setup,
for example if you forget to config the correct IP interface.
In this case tests are crashing into HardFault.
Proposition is to check the interface pointer in each tests.
Now tests are failing with more explicit status.
Thx
Impact of changes
none for well configured setup :-)
Migration actions required
Documentation
Pull request type
Test results
Reviewers