kernelci: config: reduce noise during config parsing #2989
+8
−2
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
When loading configuration files for the first time, the current job isn't configured yet and we're missing important params such as the target architecture. However, we try to parse and format every single string from the config, leading to numerous errors being printed to the console. As those are `KeyError` exceptions, we should process them separately and only print a message for other types of exceptions. Fixes kernelci#2988 Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When loading configuration files for the first time, the current job isn't configured yet and we're missing important params such as the target architecture. However, we try to parse and format every single string from the config, leading to numerous errors being printed to the console.
As those are
KeyErrorexceptions, we should process them separately and only print a message for other types of exceptions.Fixes #2988