-
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
Quick-fix running out of CASE sessions #17779
Conversation
- From project-chip#17422 onwards, "previous" CASE sessions were not expired in terms of the session cache if sessions were constantly re-established. - A root cause solution will be to solve project-chip#17568, but in the meantime, cert testing started failing after N (where N is session manager pool size) runs. This PR cleans-up the previous sessions from same node (duplicate sessions that should not happen). This is a bit unclean but will do to unblock testing since it was good enough before, and the better method is not yet implemented. This PR also adds logging when this happens. Fixes project-chip#17698 Testing done: - Unit tests pass - Cert tests pass - Manual run of N > 16 `for i in {1..18}; do ./out/debug/standalone/chip-tool basic read vendor-name 115566 0 ; done` does not fail as before.
8ec66ad
to
fa7dfe2
Compare
PR #17779: Size comparison from 6c54ab8 to fa7dfe2 Increases (32 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
Decreases (4 builds for cc13x2_26x2)
Full report (32 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
|
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.
There should a temporary solution before #17568 being fixed
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 should be a temporary solution before #17568 being fixed
Problem
in terms of the session cache if sessions were constantly
re-established.
cert testing started failing after N (where N is session manager
pool size) runs.
Fixes #17698
Change overview
This PR cleans-up the previous sessions from same node (duplicate sessions
that should not happen). This is a bit unclean but will do to unblock
testing since it was good enough before, and the better method is not
yet implemented.
This PR also adds logging when this happens.
Testing
for i in {1..18}; do ./out/debug/standalone/chip-tool basic read vendor-name 115566 0 ; done
does not fail as before.