Skip to content

Conversation

@h-vetinari
Copy link
Member

Try to see which skips we still need after 2.6, and whether we can run with -n 2 like on unix.

don't rely on PKG_BUILDNUM resolving this correctly, which is either racy,
or implicitly depends on a separate render pass after setting build.number
otherwise conda breaks
```
conda_build.exceptions.RecipeError: Mismatching hashes in recipe. Exact pins in dependencies that contribute to the hash often cause this. Can you change one or more exact pins to version bound constraints?
Involved packages were:
Mismatching package: libtorch (id cpu_generic_habf3c96_0); dep: libtorch 2.6.0.rc7 *0; consumer package: pytorch
```
and also runs into some openmp issue:
```
----------------------------- Captured stderr call -----------------------------
OMP: Error conda-forge#179: Function pthread_key_create failed:
OMP: System error conda-forge#35: Resource temporarily unavailable
```
this was done for consistency with `build.sh`, but appears unnecessary on windows
keep it on windows though, where there's no issue

This reverts commit 9fcb3a7.
@conda-forge-admin
Copy link
Contributor

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.
  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

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

@h-vetinari h-vetinari mentioned this pull request Feb 11, 2025
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.

2 participants