-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add invoke command test for invoke boundary conditions on reply too large
#30643
Closed
andy31415
wants to merge
9
commits into
project-chip:master
from
andy31415:invoke_command_tests_on_size
Closed
Changes from 3 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
a9f79e2
Start adding some tests for reply limits. Make the global bools scope…
andreilitvin a62917b
Test prepared
andreilitvin ce74753
Add bug-guards for tests to pass
andreilitvin 846c692
Tightened error type corner bounds
andreilitvin 0f3624b
Restyle
andreilitvin a360adf
Some comments
andreilitvin eaaf8c7
Add boundary test for sending too
andreilitvin 0b8454a
Add progression checks
andreilitvin 732fded
Restyle
andreilitvin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I understand this correctly it has to do with the Rollback/Checkpoint stuff. We fail in just the right way that we rollback to a state where the array closed, but the InvokeReponseMessage fails and then it proceeds to rollback
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is what the test intends to validate - I am surprised we have 2 failure modes though. For very large buffers we obviously eventually succeed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Chatted about this with Andrei. But will post here for folks reading.
The second issue
Crash due to MessageBuilder::EncodeInteractionModelRevision() encoding failure
is likely because it errors out onReturnErrorOnFailure(mInvokeResponseBuilder.EndOfInvokeResponseMessage());
here while inTryAddResponseData
, this cause a rollback wheremInvokeResponseBuilder.GetInvokeResponses().
is in the wrong state and no longer has an outer container. When it gets call a second time in theFinishStatus
here you get the error.The first error is likely some other weirdness of rollback interacting in a weird way where we end some of the containers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like OpenIOT and NRF have different limits here (guessing maybe LWIP buffer allocation ranges maybe).
I am unsure if we want to try to have this test in and then improve or just use it as a template to fix the bugs we have and then commit some version of it only once it consistently passes ...