-
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
Tests: use proper certs for Alice and Bob #18207
Conversation
PR #18207: Size comparison from 44dd01b to c3b0247 Increases (30 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, nrfconnect, telink)
Decreases (4 builds for cc13x2_26x2)
Full report (34 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
|
PR #18207: Size comparison from 2580fb3 to e3fdfb8 Increases (21 builds for cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, nrfconnect, telink)
Decreases (4 builds for cc13x2_26x2)
Full report (25 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.
This is probably no worse than what we had before, but the invariant violation is just waiting to blow up in our faces.... In particular, any time someone uses a (public key, fabric id) to identify a fabric, not a fabric index, things will break in weird ways....
@bzbarsky-apple The root problem is that the |
Yes, but the invariant in the spec is that a given stack instance has a unique node id in a given fabric, which is why the data structure looks like it does. The tests are just violating that invariant.... |
Problem
Certs for Alice and Bob in out unit-tests are wrong, they are belonged to different fabrics.
Change overview
Use new test-certs for Alice and Bob
Testing
Passed unit-tests