Closed johnkerl closed 8 months ago
With the update to tiledb 2.19, we can no longer hide from the solver problems that started with 2.18.3 and 2.18.4. I'll try to find time to investigate further later today
I haven't been able to figure out why, but for some reason, starting with tiledb 2.18.3, there is some conflict in the dependency solver for the tiledbsoma-py conda envs. The R build envs continue to be fine (they previously installed with 2.18.3, and are now happy to install with 2.19.0).
The build order this time started with the R builds, which both passed. The failure comes from the first Python build, 3.8:
BUILD START: ['libtiledbsoma-1.7.0-hd763302_0.conda', 'r-tiledbsoma-1.7.0-r43h415b3ff_0.conda', 'r-tiledbsoma-1.7.0-r42h415b3ff_0.conda', 'tiledbsoma-py-1.7.0-py38h362c0dd_0.conda', 'tiledbsoma-py-1.7.0-py310h0107f82_0.conda', 'tiledbsoma-py-1.7.0-py37h0f1fff0_0.conda', 'tiledbsoma-py-1.7.0-py39h580bbbf_0.conda']
Based on previous experience (https://github.com/TileDB-Inc/tiledbsoma-feedstock/pull/74#issuecomment-1885371268), I assume this conda solver problem will affect the Python 3.8, 3.9, and 3.10 builds
Following our established procedure this PR has done its job.
Summary: the conda solver problem in the Python build envs was due to the outdated numpy pins
We could have fixed this weeks ago in https://github.com/TileDB-Inc/tiledbsoma-feedstock/pull/74
Re-opening to implement @jdblischak advice
Green again; closing again for the same reasons.
This follows our established procedure.
As well it includes (as it must) https://github.com/TileDB-Inc/tiledbsoma-feedstock/pull/48