Conversation
now that it no longer mixes hints and lints
move it to conda-forge-specific lint
xhochy
left a comment
There was a problem hiding this comment.
Content-wise, this looks good; two minor nits that don't need to be fixed.
| ) | ||
|
|
||
| # 8. check for obsolete os_version | ||
| # 7. check for obsolete os_version |
There was a problem hiding this comment.
Unrelated nit: We're a bit inconsistent in the comments with "1." vs "1:" ;)
There was a problem hiding this comment.
Personally, I'd be more inclined to just remove the numbering. It serves no purpose, and makes it harder to move lints (if it ever becomes desirable to group or otherwise reorder checks)
| conda_build_config_keys = set() | ||
| forge_yaml = {} | ||
| # Interlude: load feedstock and recipe config | ||
| feedstock_config_keys = _get_feedstock_config(recipe_dir) |
There was a problem hiding this comment.
What's the reason you only load this here and not at the very top of the function?
There was a problem hiding this comment.
This PR was already ballooning in size, so I tried to keep changes local where possible. Further cleanups are of course possible.
h-vetinari
left a comment
There was a problem hiding this comment.
Thanks for the review!
| ) | ||
|
|
||
| # 8. check for obsolete os_version | ||
| # 7. check for obsolete os_version |
There was a problem hiding this comment.
Personally, I'd be more inclined to just remove the numbering. It serves no purpose, and makes it harder to move lints (if it ever becomes desirable to group or otherwise reorder checks)
| conda_build_config_keys = set() | ||
| forge_yaml = {} | ||
| # Interlude: load feedstock and recipe config | ||
| feedstock_config_keys = _get_feedstock_config(recipe_dir) |
There was a problem hiding this comment.
This PR was already ballooning in size, so I tried to keep changes local where possible. Further cleanups are of course possible.
|
Ah, the error finally has some more context now. "unscheduled maintenance" does not sound good. In fact, https://status.coveralls.io/ says
So I guess we can ignore this here, though we might want to break out the coverage stuff into a separate check, so that at least it becomes visible at first glance whether the tests passed or not. |
fb8840c to
ea1897f
Compare
|
Thanks for the review @xhochy! |
What started out as just wanting to rip out the logic for
MACOSX_DEPLOYMENT_TARGETbecame a deeper and deeper rabbit hole as various obvious follow-up clean-ups were blocked by the state of the code.This PR:
c_stdlib_version/MACOSX_SDK_VERSION) to simply ignoreMACOSX_DEPLOYMENT_TARGET; this showed that the merge logic contained some subtle bugs where our tests were misconfigured after reflect upcoming macos 11.0 baseline #2461, but didn't trigger (I don't expect this to affect many recipes, but strictly speaking we were missing some lints)lint_stdlibto a separate lint that's conda-forge-specificMACOSX_DEPLOYMENT_TARGETconda_build_config.yamlin v1 recipes (e.g. the state before Rebuild for aws-crt-cpp 0.37.3 aws-sdk-cpp-feedstock#993 didn't actually trigger a linter warning despite the outdated pins)conda_build_config.yamlas well asvariants.yamlare in the recipe folderAll the commits have been individually tested and I highly recommend to review them one-by-one (consider each as a mini-PR; the overall diff is too messy).