Skip to content
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

config_load should error (by default) instead if file is not found #684

Open
PGijsbers opened this issue Dec 24, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@PGijsbers
Copy link
Collaborator

Currently when loading/specifying a file in the configuration, e.g., a framework file, if there is a typo the file is ignored and a warning is given. It would be a lot easier to track issues down with e.g., spelling errors (which are not checked in the yaml configuration), if the benchmark would just stop right there with an error.

I am not sure why a warning is given instead of an error. This warrants some investigation, perhaps this is to make some special run mode or some preconfigured defaults work (like user configurations). Should check this before changing the behavior. Alternatively it could stay warning by default and optionally error through a configuration option.

@PGijsbers PGijsbers added the enhancement New feature or request label Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant