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
One trick that might help would be to have a separate CI job which unpacked the contents of the just-built package and called tree on it. With GitHub Actions you could even output the result as a job summary - something like:
The idea is to have the logs report the contents of the artefacts (and their sizes) to easily check what has been included in the conda package. Very useful for staged-recipes reviews (did a package named tests got included?) and in-feedstock debugging (where's my library?!).
The text was updated successfully, but these errors were encountered:
As @dhirschfeld mentioned in conda/conda-package-handling#5 (comment):
The idea is to have the logs report the contents of the artefacts (and their sizes) to easily check what has been included in the conda package. Very useful for staged-recipes reviews (did a package named
tests
got included?) and in-feedstock debugging (where's my library?!).The text was updated successfully, but these errors were encountered: