-
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
Initialize CHIP stack before running app tests #29092
Conversation
Yes, that's what I think as well. So, I've converted this to draft for now until I will investigate why it's failing. |
086d53c
to
79087ee
Compare
PR #29092: Size comparison from 433e676 to 79087ee Increases (5 builds for cc32xx, psoc6)
Full report (32 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, k32w, linux, mbed, psoc6, qpg)
|
79087ee
to
c2812f2
Compare
PR #29092: Size comparison from 4a9dab1 to c2812f2 Increases (5 builds for cc32xx, psoc6)
Full report (80 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
a5388e2
to
5711a1a
Compare
PR #29092: Size comparison from a40b53c to 5711a1a Increases (17 builds for telink)
Full report (80 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
PR #29092: Size comparison from 1ec98c8 to 846b9db Decreases (1 build for telink)
Full report (80 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
PR #29092: Size comparison from 5647e0a to f8b2ba1 Full report (82 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
* Initialize CHIP stack before running app tests * Patch add_entropy_source() to make it idempotent * Do not add entropy source more than once
Problem
When running
TestCommandInteraction
test (and potentially other tests from src/app/tests), one ofchip::System::LayerImplSelect::mWakeEvent
objects is not properly initialized. It results inWakeEvent::Notify()
writing tomWriteFD == 0
(in fact the0
value is a not initialized memory) which definitely is not right.Changes
chip::DeviceLayer::SystemLayerImpl()
) before running testsTesting
Tested manually that there are no writes to mWriteFD==0 any more. CI will check for potential test failures.