search

TileDB-Inc / tiledbsoma-feedstock

A conda-smithy repository for tiledbsoma.
BSD 3-Clause "New" or "Revised" License
3 stars 3 forks source link

linux-64 build now requires libgoogle-cloud 2.24 #155

Closed jdblischak closed 1 month ago

jdblischak commented 1 month ago

The linux-64 job failed on the merge commit (https://github.com/TileDB-Inc/tiledbsoma-feedstock/commit/f537d2dbc8d7e195dac350578fd8b0ca031cd67a) from my recent PR #154 to update for Python 3.12.

Could not solve for environment specs
The following packages are incompatible
├─ libgoogle-cloud-storage 2.24.0.* h3d9a0c8_0 is requested and can be installed;
└─ libtiledbsoma 1.11.1.* h6216f82_0 is not installable because there are no viable options
   ├─ libtiledbsoma 1.11.1 would require
   │  └─ tiledb >=2.23.0,<2.24.0a0 , which requires
   │     └─ libgoogle-cloud-storage >=2.23.0,<2.24.0a0 , which conflicts with any installable versions previously reported;
   └─ libtiledbsoma 1.11.1 conflicts with any installable versions previously reported.

Thus it clearly needs tiledb-feedstock to be migrated to libgoogle-cloud 2.24. The PR is open, https://github.com/conda-forge/tiledb-feedstock/pull/285#issuecomment-2117978773, but it is blocked by an unexpected win-64 build failure that we first discovered last week in our nightly feedstock builds (https://github.com/TileDB-Inc/conda-forge-nightly-controller/issues/94)

jdblischak commented 1 month ago

https://github.com/conda-forge/tiledb-feedstock/pull/285#issuecomment-2117978773 was merged last night. This morning I restarted the failed linux-64 build on commit https://github.com/TileDB-Inc/tiledbsoma-feedstock/commit/f537d2dbc8d7e195dac350578fd8b0ca031cd67a, and it passed.

And strangely an entire new job was also started even though I clearly clicked in the GitHub checks UI to only re-run failed jobs. This same thing happened recently to me where I restarted a failed job on a merge commit in another feedstock. This is really frustrating since it is a waste of CI resources. And I don't want to cancel it because it replaces the CI links attached to the commit, so it would like it failed.