tests: Bluetooth: Classic: GAP_S: Fix case tc_gap_s_2 failure issue #100206
+3
−0
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 the case, when the connection is established on the local side, the test script will require peer device to send ACL disconnection request. But due to the timing issue, the connected event may be not notified on the peer device side when the peer device received the ACL disconnection requirement. The exception will happen. It causes the case to fail. Wait for the connected event of the peer device before sending the ACL disconnection request. Signed-off-by: Lyle Zhu <[email protected]>
zephyrbot
added
area: Bluetooth
area: Tests
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.
In the case, when the connection is established on the local side, the test script will require peer device to send ACL disconnection request. But due to the timing issue, the connected event may be not notified on the peer device side when the peer device received the ACL disconnection requirement. The exception will happen. It causes the case to fail.
Wait for the connected event of the peer device before sending the ACL disconnection request.