Matthew R. Becker
Matthew R. Becker
I'd rather have the table file in the same spot as the metadata package along with the code to make it. We can version it separately ofc.
A few comments: - We don't need to update the mapping more than once a week IMHO. - The conda-forge-metadata repo is already taken by the package to read the...
Thanks a bunch and no worries. Ad hoc things have been the issue for this task, so the discussion is helpful to remove that ambiguity. - We should store the...
The three things I have gotten rid of are: - libcfgraph: code (https://github.com/regro/libcflib) and data (https://github.com/regro/libcfgraph) - repodata generation outside of anaconda.org: code (https://github.com/conda-forge/repodata-tools), repoodata (https://github.com/conda-forge/repodata) and repodata shards (https://github.com/conda-forge/repodata-shards)...
Look at our feedstock-outputs repo. Each package has a json file in that repo.
@conda-forge/core it has been two weeks on this PR and there are no other reviews. Shall we merge?
So the test jobs marked as "serial" are being run with two pytest-xdist workers. Is that maybe the issue?
Maybe add some retry test markers to have the test suite try twice as a stopgap?
Hrmmm. Can we try things actually in serial as a test?
I am -1 to merging this PR in general.