tests/ieee802154: Fix how is initialized the driver lock in l2 test #650
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.
The test starts the last one: after the driver and the net stack.
However, the net stack (due to DAD and else) will already try to send
some packet, resulting in giving an uninitialized semaphore. But once
properly initialized, this semaphore will end up with a non-zero count
when the test will start: thus resetting it to 0 before running the
tests.
Jira: ZEP-2319
Reported-by Andrew Boie [email protected]
Signed-off-by: Tomasz Bursztyka [email protected]