-
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
[PICS] Update PICS.yaml with the latest PICS from the test plan, upda… #24923
[PICS] Update PICS.yaml with the latest PICS from the test plan, upda… #24923
Conversation
PR #24923: Size comparison from c49ee00 to 09bb896 Increases (1 build for cc32xx)
Full report (1 build for cc32xx)
|
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.
Assuming this ends up running/skipping the same set of tests as before, looks good.
…te ci-pics-values accordingly and add many missing keys, remove some unknown keys, fix some mistype keys and apply the relevant changes to the related testcases
09bb896
to
18db7cc
Compare
PR #24923: Size comparison from c49ee00 to 18db7cc Increases (2 builds for cc32xx, nrfconnect)
Full report (10 builds for cc32xx, k32w, mbed, nrfconnect, qpg)
|
I looked at how many steps are skipped before and after this change. In both cases the CI is skipping 666 steps at the moment. |
…te ci-pics-values accordingly and add many missing keys, remove some unknown keys, fix some mistype keys and apply the relevant changes to the related testcases
Problem
I initially found that
PICS_MCORE_UI_FACTORYRESET
andMCORE.FACTORY_RESET
coexists in our YAML tests.I then tried to update the
PICS.yaml
file that is the reference for our default CI PICS configuration at src/app/tests/suites/certification/ci-pics-valuesIt appears that they were a lot of differences between the latest PICS database and ours. I have updated
PICS.yaml
andci-pics-values
to reflect that. I have also updated out tests suites to reflect that.The test plan database was missing some keys as well. I have opened https://github.com/CHIP-Specifications/chip-test-plans/pull/2427 for that...