-
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
Remove Test*.py scripts from excluded list and enabling its execution via glob python test runner #35795
Conversation
Review changes with SemanticDiff. Analyzed 7 of 8 files.
|
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.
Lets not do this: the runner should be an integration runner and not a path of "run arbitrary python code" just because it can.
Instead pure python tests should be part of BUILD.gn unit testing, since this is what they are: unit tests. Adding them to a test runner increases the complexity of executing them. |
PR #35795: Size comparison from bb9363d to 7e40f89 Full report (88 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
This PR is closed for now, the work will be carried over as a follow-up task to the PR #34785. |
Work for Issue #31317
Follow up to PR #35660
PR 19 - This PR modifies the test infrastructure by removing
Test*.py
scripts from the excluded list and ensuring they are now automatically included in test runs using the glob pattern in the Python test runner script.