Skip to content

Migration to rattler-build, added specific Python tests - #42

Merged
toniher merged 3 commits into
conda-forge:mainfrom
toniher:python-tests
Jul 3, 2026
Merged

Migration to rattler-build, added specific Python tests#42
toniher merged 3 commits into
conda-forge:mainfrom
toniher:python-tests

Conversation

@toniher

@toniher toniher commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

This pull request migrates the build system from conda-build to rattler-build and updates the recipe format from meta.yaml to the new recipe.yaml schema. It also refactors the build scripts for all supported platforms (Linux, macOS, Windows) to use rattler-build commands and options.

Migration to rattler-build and new recipe format:

  • Switched the build tool from conda-build to rattler-build in all CI scripts (.scripts/build_steps.sh, .scripts/run_osx_build.sh, .scripts/run_win_build.bat), including corresponding command-line option updates and environment setup changes.
  • Updated conda-forge.yml to specify conda_build_tool: rattler-build for the new build backend.
  • Replaced the legacy meta.yaml recipe with a new recipe.yaml using the rattler-build schema, including explicit build, host, run requirements, and expanded test cases.

Build script improvements:

  • Unified and modernized test skipping and metadata handling options across platforms, using --test skip and repeated --extra-meta flags for better compatibility with rattler-build.

Testing enhancements:

  • Added new test scripts test.py and test_gguf.py to the recipe, with test_gguf.py performing an end-to-end model load, tokenization, inference, and embedding check using a real GGUF model.

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.

This should close #41

toniher and others added 2 commits July 3, 2026 15:45
Replace conda-build with rattler-build across all build scripts and convert
meta.yaml to rattler-build's recipe.yaml format. Add comprehensive Python test
suite including basic import checks and GGUF model inference testing. Update
build configuration to use conditional logic for platform-specific commands.
The conda-smithy rerender regenerated README.md badges using the local
directory name, producing a non-existent repo slug
(llama-cpp-python-feedstock.python-tests-feedstock) and definitionId=None.
Revert README to the original canonical badges.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@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/recipe.yaml) and found it was in an excellent condition.

@jjerphan

jjerphan commented Jul 3, 2026

Copy link
Copy Markdown
Member

@conda-forge-admin, please rerender

@jjerphan jjerphan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM modulo build number bump and green CI checks.

Comment thread recipe/recipe.yaml Outdated
@conda-forge-admin

Copy link
Copy Markdown
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/28666345804. Examine the logs at this URL for more detail.

Co-authored-by: Julien Jerphanion <git@jjerphan.xyz>
@toniher
toniher merged commit 617a9f3 into conda-forge:main Jul 3, 2026
23 checks passed
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.

Test for the package once created

3 participants