-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Troubleshoot solver error #20
Conversation
A useful signal. The build log I inspected yesterday failed when trying to build the first Python client, which just happened to be Python 3.10 (as far as I can tell, the order of the Python builds is random). However, today, the builds succeeded for Python 3.7 and 3.8 before failing with 3.10 BUILD START: ['libtiledbsoma-1.2.2-h25619bb_1.conda', 'tiledbsoma-py-1.2.2-py38h025a340_1.conda', 'tiledbsoma-py-1.2.2-py37hb397f5f_1.conda', 'tiledbsoma-py-1.2.2-py310h40e830b_1.conda', 'tiledbsoma-py-1.2.2-py39h4be961d_1.conda'] So there is something about Python 3.10 that is causing the solver error. Still unknown if Python 3.9 will work or not |
Python 3.9 built successfully as well. Thus this solver error is limited to Python 3.10 |
I'm going to let this sit for now, and return later once libtiledb has been built with libgoogle-cloud 2.10 (conda-forge/tiledb-feedstock#188) |
Thanks @jdblischak !! :) |
Alright, merging conda-forge/tiledb-feedstock#188 to build libtiledb against libgoogle-cloud 2.10 fixed the solver error for Python 3.10. This gets us unstuck for now |
The recipe that successfully built last week (bb3fbeb) is now failing. Specifically, libtiledbsoma builds fine, but then the Python client build fails because conda isn't able to solve the environment:
Some incompatibility has arisen somewhere in the dependency chain. I'm using this PR to troubleshoot
xref: #18