Details
- Reviewers
olasd - Group Reviewers
Reviewers - Commits
- rDCORE24f9d5ee2b73: Log used config files.
Diff Detail
- Repository
- rDCORE Foundations and core functionalities
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
Build is green
See https://jenkins.softwareheritage.org/job/DCORE/job/tox/114/ for more details.
swh/core/config.py | ||
---|---|---|
101 | That's an info at best, as it'd log an error message if a config file voluntarily doesn't exist (e.g. during tests). exists_accessible already raises relevant errors when a file is present but inaccessible. |
That's an info at best, as it'd log an error message if a config file voluntarily doesn't exist (e.g. during tests).
exists_accessible already raises relevant errors when a file is present but inaccessible.
We agreed that tests should not try to load config files. And allowing config files to be missing without reporting errors is asking for trouble.
Okay?
And allowing config files to be missing without reporting errors is asking for trouble.
All the systems currently in production depend on this behavior: they try to load local configuration (in ~/.config), which fails (expectedly!), then they load the configuration in /etc.
All in all I don't think all workers should immediately start spewing a handful of error messages at each run for something that is _expected_.
I'd even go as far as putting those messages at DEBUG level.
Build is green
See https://jenkins.softwareheritage.org/job/DCORE/job/tox/116/ for more details.
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DCORE/job/tox/119/
See console output for more information: https://jenkins.softwareheritage.org/job/DCORE/job/tox/119/console
That's an info at best, as it'd log an error message if a config file voluntarily doesn't exist (e.g. during tests).
exists_accessible already raises relevant errors when a file is present but inaccessible.