Fix test for symlink and move tests to top level.

[bdice]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

While reviewing conda-forge/staged-recipes#21902, I noticed that the tests for libcublas on Linux were checking if libcublas.so.12 is a file and libcublas.so.12.0.1.189 is a symlink. However, that's backwards. libcublas.so.12 should be a symlink pointing to libcublas.so.12.0.1.189. I'm not sure how this passed CI before, because test -L $PREFIX/targets/{{ target_name }}/lib/libcublas.so.{{ version }} should not pass from what I can tell.

[conda-forge-webservices]

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 (recipe) and found it was in an excellent condition.

[bdice]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/libcublas-feedstock/actions/runs/4647093322.

[adibbley]

@bdice was there anything else you wanted to add here? Looks like it is marked as draft so wanted to be sure before I merge

[bdice]

@adibbley Yes, I mentioned this to @jakirkham and these tests aren’t running. We probably have to put the tests for libcublas in the top level instead of the subpackage output because of the name conflict. Haven’t made that change yet but will do so soon.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• The top level meta keys are in an unexpected order. Expecting ['package', 'source', 'build', 'test', 'outputs', 'about', 'extra'].

[conda-forge-webservices]

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 (recipe) and found it was in an excellent condition.

[jakirkham]

So just to confirm, moving these tests to the top-level worked?

If so, would move these to after outputs, but before about in the top-level portion of the recipe

[bdice]

Yes, moving this to the top level worked. I verified in the CI output.

The conda-forge linter won't let us put this key in any other place:

For recipe:

• The top level meta keys are in an unexpected order. Expecting ['package', 'source', 'build', 'test', 'outputs', 'about', 'extra'].

[bdice]

@adibbley This should be ready to merge when you're able.