tests: Bluetooth: Classic: Fix sm_key_persist_004 failure issue #100204
+11
−2
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
For the case sm_key_persist_004, the disconnected event may be printed before the log `Pairings successfully cleared` since there is no order between log `Pairings successfully cleared` and the disconnected event. It causes the script discards the disconnected event in this case and rise the assert issue. For the case sm_key_persist_004, check the disconnected event in the captured log. If it is not found, wait the disconnected event until timeout. Signed-off-by: Lyle Zhu <[email protected]>
zephyrbot
added
area: Bluetooth Classic
zephyrbot
requested review from
MarkWangChinese,
chengkai15,
gzh-terry,
jhedberg,
makeshi and
nashif
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
For the case sm_key_persist_004, the disconnected event may be printed before the log
Pairings successfully clearedsince there is no order between logPairings successfully clearedand the disconnected event. It causes the script discards the disconnected event in this case and rise the assert issue.For the case sm_key_persist_004, check the disconnected event in the captured log. If it is not found, wait the disconnected event until timeout.