Skip to content

cutensor v2.1.0.9 #65

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

Merged
merged 25 commits into from
Jan 31, 2025
Merged

Conversation

regro-cf-autotick-bot
Copy link
Contributor

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

  • Dependencies have been updated if changed: see upstream
  • Tests have passed
  • Updated license if changed and license_file is packaged

Information about this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version.
  3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
  4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
  5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name Upstream Version Current Version
cudatoolkit 12.0.0 Anaconda-Server Badge
git 2.48.1 Anaconda-Server Badge

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/13020924503 - please use this URL for debugging.

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Jan 28, 2025

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/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

  • ❌ You are setting c_stdlib_version below the current global baseline in conda-forge (10.13). If this is your intention, you also need to override MACOSX_DEPLOYMENT_TARGET (with the same value) locally.

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13056533239. Examine the logs at this URL for more detail.

@carterbox
Copy link
Member

The problem is the bot didn't update the hashes correctly, so couldn't download any of the tarballs.

@carterbox
Copy link
Member

@conda-forge-admin, please rerender

@jakirkham
Copy link
Member

Thanks Daniel! 🙏

Looks like we need GLIBC 2.28

Basing this on this CI failure:

binary glibc 2.27.0 <= recipe glibc 2.17 <= system glibc 2.34 $PREFIX/lib/libcutensorMg.so.2.1.0

@carterbox
Copy link
Member

The Windows build fails because the runner doesn't have enough space to unpack the zip. Probably this is related to the fact that all builds of cutensor are shipped in the same archive instead of separately for CTK 11 and CTK 12.

@carterbox
Copy link
Member

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Jan 30, 2025

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/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13080657240. Examine the logs at this URL for more detail.

recipe/bld.bat Outdated
Comment on lines 3 to 21
:: Hack to free up additional space on Azure
:: Replace with conda-smithy solution when available
:: xref: https://github.com/conda-forge/conda-smithy/pull/1966
if "%CI%" == "azure" (
set CLEANUP_DIRS=^
C:\hostedtoolcache\windows;^
;

mkdir C:\empty
for %%f in (%CLEANUP_DIRS:;= %) do (
if not [%%f] == [] (
echo Removing %%f
dir %%f
robocopy /mir /mt /zb /ns /nc /nfl /ndl /np /njh /njs C:\empty %%f > nul 2>&1
rmdir /q %%f
)
)
rmdir /q C:\empty
)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have found C:\hostedtoolcache\windows takes up a fair bit of space on Azure. Removing it would free up that space

Had put this solution together in this conda-smithy PR: conda-forge/conda-smithy#1966

Though have not found a good method for deleting this directory quickly on Windows. So the deletion takes a while. Maybe acceptable if there is no other option (like we see here)

That said, if we could find a faster way to do this deletion, it would be easier to integrate this approach in conda-smithy and just enable with a config parameter

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Though have not found a good method for deleting this directory quickly on Windows.

Which options have you tried?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did the bulk of the exploration in these PRs:

With matplotlib, it was picking up some VM Python during its build and getting hosed. We were not able to get the build to stop picking up the VM Python and couldn't figure out why it was showing up. So we went with the deletion option to get the build fixed up. Lots of commits in there trying things

Though running out of space is an often enough problem (like with this update), that I found the simplest out-of-the-way Windows only build and used that for testing, which is why MiKTeX was used. It was also simpler than going through a full matplotlib build each iteration

Tried different deletion methods. Found robocopy was better than the others. So then tweaked options to eek out more performance

If you spot something I've missed, would be curious to learn about it

Avoids a bug in some recent `patchelf` versions. Ideally would relax
this in the future once that issue is fixed.
As `patchelf` is a build tool, it can be in `requirements/build`.
recipe/meta.yaml Outdated
@@ -50,8 +41,10 @@ requirements:
- {{ compiler('cxx') }}
- {{ compiler('cuda') }}
- arm-variant * {{ arm_variant_type }} # [aarch64]
- cf-nvidia-tools # [linux]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added cf-nvidia-tools and switched to it for our GLIBC check

Think I got the related bits replaced. Though please let me know if I've missed something

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@carterbox carterbox Jan 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- cf-nvidia-tools # [linux]
- cf-nvidia-tools 1 # [linux]

Also, maybe we want to be conservative and pin to the major version to protect against breaking changes?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there particular breaking changes you have in mind?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not currently, but I've promised to use actual semantic versioning for this package. I suspect there may be breaks once we start adding more features to cf-nvidia-tools and the complexity increases.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok let's make sure this goes in the migrator and other used places

Bots already will sort the keys in `conda-forge.yml` when changing them.
So go ahead and sort them proactively.
@jakirkham
Copy link
Member

@conda-forge-admin , please re-render

@conda-forge-admin
Copy link
Contributor

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/conda-forge-webservices/actions/runs/13064835195. Examine the logs at this URL for more detail.

This cleanup needs to happen before the `redist` is downloaded.
Otherwise we run out of space when downloading or uncompressing it. So
use a custom CI setup script to do this cleanup during CI setup before
the recipe build has started.
@jakirkham
Copy link
Member

@conda-forge-admin , please re-render

conda-forge-webservices[bot] and others added 5 commits January 31, 2025 03:30
Something funky is happening with this variable where nothing is
actually iterated over and removed in the `for`-loop. Try setting this
outside the `for`-loop in case the indenting is somehow causing syntax
issues when parsing the list.
This drive has more space. So hopefully switching to it avoids the space
issues we have seen.
@jakirkham
Copy link
Member

@conda-forge-admin , please re-render

conda-forge-webservices[bot] and others added 2 commits January 31, 2025 04:51
@jakirkham
Copy link
Member

@conda-forge-admin , please re-render

Copy link
Member

@carterbox carterbox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once patchelf is removed from the deps, LGTM.

jakirkham and others added 2 commits January 31, 2025 12:56
@jakirkham jakirkham requested a review from carterbox January 31, 2025 20:58
@carterbox carterbox merged commit 5c5dd0c into conda-forge:main Jan 31, 2025
9 checks passed
@regro-cf-autotick-bot regro-cf-autotick-bot deleted the 2.1.0.9_h98a7bf branch January 31, 2025 21:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants