Nightly builds started failing on 2023-01-16 about conda-forge-nightly-controller

[shaunrd0]

Thanks John, I've re-enabled these workflows for you. If there's anything else I can do here please let me know, happy to help.

[jdblischak]

Found it!

The Python pins in conda-forge-pinning are incompatible with setuptools 66+

conda-forge/conda-forge-pinning-feedstock#3973

4 days ago they pushed repodata patches to pin setuptools <66.0.0a for the conda-build binaries on anaconda.org

conda-forge/conda-forge-repodata-patches-feedstock#387

Since these changes should by synced by now, the nightly builds should pass tonight 🤞

[jdblischak]

I believe the source of the error is the recent update in setuptools 66.0 that made it more strict to allowable version strings: pypa/setuptools#3772

pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '3.8.* *_cpython'

I confirmed that the most recent successful build used setuptools 65.6.3 and the failed build used setuptools 6.66.0

But still unsure how to fix it. The discussion in the setuptools repo is mostly fixing the version strings of system Python packages installed by APT, which doesn't apply to us. We're already using a virtual (conda) env, which is the recommended workaround. And the upstream feedstocks don't appear to have this problem (yet, I guess), so why are we experiencing it?

[jdblischak]

I confirmed that setuptools 65.6.3 is installed when running locally:

bash run-local-tiledb.sh
mamba list -n env-nightlies-tiledb setuptools
## # Name                    Version                   Build  Channel
## setuptools                65.6.3             pyhd8ed1ab_0    conda-forge

bash run-local-tiledb-py.sh
## error: failed to push some refs to 'https://github.com/TileDB-Inc/tiledb-py-feedstock.git'
mamba list -n env-nightlies-tiledb-py setuptools
## # Name                    Version                   Build  Channel
## setuptools                65.6.3             pyhd8ed1ab_0    conda-forge
## setuptools-scm            7.1.0              pyhd8ed1ab_0    conda-forge

The failure when updating TileDB-Py is irrelevant. I don't have write access to TileDB-Inc/tiledb-py-feedstock, and it happens to be a few commits behind the upstream conda-forge feedstock (whereas TileDB-Inc/tiledb-feedstock is in sync)

[jdblischak]

Good news. Now that Shaun re-enabled the workflows and the conda-forge team patched conda-build to use setuptools<66, the scheduled nightly builds both passed

• tiledb
• tiledb-py

The tiledb feedstock Azure build passed and uploaded binaries for 2.15.0.2023_01_23. However, the tiledb-py feedstock Azure builds all failed, but I think this is a known issue since the nightly builds on the source repo have also been failing, eg TileDB-Inc/TileDB-Py#1584