Allow wildcards in filter file #166
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Each test filter is passed into a regex, then every test is matched against said regex. Signed-off-by: Camila Alvarez <cam.alvarez.i@gmail.com>
Signed-off-by: Camila Alvarez <cam.alvarez.i@gmail.com>
Signed-off-by: Camila Alvarez <cam.alvarez.i@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
--filteroption allows passing a file that will work as a filter for picking results for a set of devices and tests. The filters are strict in the sense that the test path must match the filter exactly to be included in the results.This PR allows referencing both hardware and tests using wildcards.
All of the follow would now be considered a valid reference to a test or set of tests:
kunit,kunit.*,kselftest.iommu.*.The new format would support a file like this:
closes #163