mypytest: support alternatives and wildcards in ntfc.yaml requirements - #18
Open
raiden00pl wants to merge 1 commit into
Open
mypytest: support alternatives and wildcards in ntfc.yaml requirements#18raiden00pl wants to merge 1 commit into
raiden00pl wants to merge 1 commit into
Conversation
Requirements only supported exact [key, value] matching, which cannot express init configuration that differs between build modes: flat builds use CONFIG_INIT_ENTRYPOINT, kernel builds CONFIG_INIT_FILEPATH. Add, backward compatibly: - [key, "*"]: any truthy value satisfies - [[key, value], ...]: alternatives, any one satisfies Also name the product, core and unmet requirement in the abort message. Signed-off-by: raiden00pl <raiden00@railab.me> Assisted-by: Claude Code
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Requirements only supported exact [key, value] matching, which cannot express init configuration that differs between build modes: flat builds use CONFIG_INIT_ENTRYPOINT, kernel builds CONFIG_INIT_FILEPATH. Add, backward compatibly:
Also name the product, core and unmet requirement in the abort message.