-
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
Better test discovery #12292
Better test discovery #12292
Conversation
fast track: test change only which should result in a noop. |
PR #12292: Size comparison from 514cf19 to 591d340 Full report (38 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, 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.
Please use the list
command. That should be less error-prone.
PR #12292: Size comparison from 800bd23 to 275dce4 Decreases (1 build for linux)
Full report (38 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Co-authored-by: Victor Morales <chipahuac@hotmail.com>
PR #12292: Size comparison from 7e99454 to 426da92 Full report (38 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
PR #12292: Size comparison from 7e99454 to d15d7c3 Full report (38 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Problem
Searching for YAML files for figuring out what tests are valid assumes that chip-tool and source code are in sync (which is not always the case) and error prone (we have many yaml files).
Change overview
Execute chip-tool itself to figure out what tests are available
Testing
Validated that
./scripts/tests/run_test_suite.py list
is identical before and after