-
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
Implement python test for TC_DGSW_2_2 #36900
base: master
Are you sure you want to change the base?
Implement python test for TC_DGSW_2_2 #36900
Conversation
Changed Files
|
PR #36900: Size comparison from 238e801 to 1635ecc Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
PR #36900: Size comparison from 238e801 to f5c9315 Full report (3 builds for cc32xx, stm32)
|
PR #36900: Size comparison from 238e801 to a6d7fd3 Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
a6d7fd3
to
c52888b
Compare
PR #36900: Size comparison from c1afc02 to c52888b Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
c52888b
to
4e6ffb3
Compare
PR #36900: Size comparison from c1afc02 to 4e6ffb3 Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
4e6ffb3
to
c92a2b9
Compare
PR #36900: Size comparison from c1afc02 to c92a2b9 Full report (42 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, nrfconnect, psoc6, qpg, stm32, telink, tizen)
|
c92a2b9
to
2ceabb5
Compare
PR #36900: Size comparison from c1afc02 to 2ceabb5 Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
2ceabb5
to
7fde5de
Compare
PR #36900: Size comparison from 2249628 to 7fde5de Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
|
||
async def send_software_fault_event(self, endpoint, pid): | ||
# Construct the FIFO path. The PID should be known beforehand or discovered as part of the setup. | ||
fifo_path = f"/tmp/chip_lighting_fifo_{pid}" |
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 works only for linux platforms. Can we implement the trigger using a test event trigger as a generic mechanism ?
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.
@cjandhyala I think fifo was introduced to replace software interrupt as a generic mechanism to simulate event trigger on posix platforms, the more generic mechanism will be non-generic cluster command, do we really want that?
Implement python test for TC_DGSW_2_2
Run test:
python3 TC_DGSW_2_2.py --commissioning-method on-network --discriminator 3840 --passcode 20202021 --storage-path admin_storage.json