You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In conda-forge/staged-recipes#28268 (comment)@ocefpaf gave a very useful short summary of the conditions for a noarch: python build to be allowed to fail on Windows in conda-forge/staged-recipes when I forgot the workflow (which is don't leave in a skip: true # [win] but remove any skip and let it fail on Windows with an explanation, given that noarch: python build on feedstock are just Linux x86 jobs).
Copying the summary from the post:
Noarch don't need to be built for all archs, we save resources that way. If this is a noarch that really needs to skip Windows we need to know:
If the reason for the skip is a missing dependency, then remove this, let it fail, and the package won't be installable on Windows until that dependency is available.
If the reason is b/c the package will get built but won't work on Windows, then you need to do a OS-noarch. Check our docs on how to do that.
If the reason is some other failure, then you may be creating a broken package by using noarch and we need to fix that failure first.
I think this would be very useful to add to the linter output beyond the existing
"`noarch` packages can't have skips with selectors. If "
"the selectors are necessary, please remove "
f"`noarch: {noarch_value}`."
noarch packages can't have skips with selectors. If the selectors are necessary, please remove noarch: python.
as I think without this information most people assume that the linter is telling them they can't have a noarch package because they assume that they can't have any failures, which results in extra builds that aren't needed.
The text was updated successfully, but these errors were encountered:
In conda-forge/staged-recipes#28268 (comment) @ocefpaf gave a very useful short summary of the conditions for a
noarch: python
build to be allowed to fail on Windows inconda-forge/staged-recipes
when I forgot the workflow (which is don't leave in askip: true # [win]
but remove anyskip
and let it fail on Windows with an explanation, given thatnoarch: python
build on feedstock are just Linux x86 jobs).Copying the summary from the post:
I think this would be very useful to add to the linter output beyond the existing
conda-smithy/conda_smithy/linter/lints.py
Lines 358 to 360 in 2b18d8d
as I think without this information most people assume that the linter is telling them they can't have a
noarch
package because they assume that they can't have any failures, which results in extra builds that aren't needed.The text was updated successfully, but these errors were encountered: