run test-suite (and repack netlib) for blis#62
Conversation
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
Getting an error Based on the number of resolution steps before, I'm guessing this happens for |
|
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug. |
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
FWIW, I don't like repackaging the netlib variant of lapack as blis. With the current scheme, it's obvious that we are using BLAS from blis and LAPACK from netlib. With the new scheme, it's not obvious whether LAPACK comes from netlib or flame or other source. |
It's a point I expected to discuss with you. ;-) But right now I was just trying to figure out how to run the test suite for blis here... Not sure if conda could be taught to correctly resolve the exact subpackage pins mixed with other variants, but so far, the only thing I've gotten working is a repack. I had an intermediate version (lost since the rebase) of renaming the |
|
Also, I now have a running test suite for blis on windows, and the results are bad: |
On second thought - all the |
…da-forge-pinning 2021.01.08.18.10.03
h-vetinari
left a comment
There was a problem hiding this comment.
@isuruf, this should be ready for a first round of discussions - not saying repacking is a must, but I believe (with the build string distinction) it's definitely feasible without ambiguity.
| - {{ pin_subpackage("blas-devel", exact=True) }} | ||
| - {{ pin_subpackage("blas", exact=True) }} |
There was a problem hiding this comment.
Yes that's a mistake and should be removed. blas should depend on blas-devel.
There was a problem hiding this comment.
I thought it was the other way around? Kinda like blas-devel > blas (in terms of dependencies)
At least that's how I've understood the -dev[el] packages in various distros, for example.
| - liblapacke {{ version }} *netlib # [blas_impl == 'blis'] | ||
| - {{ pin_subpackage("libcblas", exact=True) }} | ||
| - {{ pin_subpackage("libblas", exact=True) }} | ||
| - {{ pin_subpackage("blas-devel", exact=True) }} |
There was a problem hiding this comment.
Same here, not sure why blas should need e.g. mkl-devel?
|
Ping @isuruf :) |
|
@isuruf |
|
@isuruf |
|
I'm not a fan of this. I believe we can test this by creating the symlinks for blis in the testing script. I'll have a look, but will not be soon. |
|
ok, thanks for the response. If you can outline your plan (e.g. symlink what to where), I can give it a shot. In the meantime, I'm placing this PR in draft mode. |
|
Thanks @h-vetinari for all your efforts. I think what we need to do is in |
|
OK, I'll think about it and might give it a shot. While we're at it, could you briefly comment on this? Circular dependencies sound bad to me, and should probably be fixed ASAP independently of the blis-stuff. |
|
Obsoleted by #65 |
No description provided.