Skip to content

faiss-split v1.12.0#91

Closed
regro-cf-autotick-bot wants to merge 2 commits into
conda-forge:mainfrom
regro-cf-autotick-bot:1.12.0_ha8d969
Closed

faiss-split v1.12.0#91
regro-cf-autotick-bot wants to merge 2 commits into
conda-forge:mainfrom
regro-cf-autotick-bot:1.12.0_ha8d969

Conversation

@regro-cf-autotick-bot
Copy link
Copy Markdown
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.

Closes: #83
Closes: #88

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
ctng-compilers 15.2.0 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/16917981212 - please use this URL for debugging.

@conda-forge-admin
Copy link
Copy Markdown
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.
  • ℹ️ faiss output has some malformed specs:
  • In section host: libfaiss =1.12.0=*_cuda
  • In section run: libfaiss =1.12.0=*_cuda
  • In section test: libblas =*=*mkl
    faiss-cpu output has some malformed specs:
  • In section run: faiss =1.12.0=*_cpu
    faiss-gpu output has some malformed specs:
  • In section run: faiss =1.12.0=*_cuda
    Requirement spec fields should match the syntax name [version [build]]to avoid known issues in conda-build. For example, instead of name =version=build, use name version.* build. There should be no spaces between version operators and versions either: python >= 3.8 should be python >=3.8.

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

@regro-cf-autotick-bot regro-cf-autotick-bot mentioned this pull request Nov 13, 2025
3 tasks
@regro-cf-autotick-bot regro-cf-autotick-bot mentioned this pull request Mar 19, 2026
3 tasks
@regro-cf-autotick-bot
Copy link
Copy Markdown
Contributor Author

I see that this PR has conflicts, and I'm the only committer. I'm going to close this PR and will make another one as appropriate. You should expect to wait at least a few hours, or possibly much longer, for a new PR.

This was generated by https://github.com/regro/cf-scripts/actions/runs/23377966742 - please use this URL for debugging.

@regro-cf-autotick-bot regro-cf-autotick-bot deleted the 1.12.0_ha8d969 branch March 21, 2026 10:52
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