Skip to content

Add inference test for built package - #38

Closed
toniher wants to merge 2 commits into
mainfrom
tests
Closed

Add inference test for built package#38
toniher wants to merge 2 commits into
mainfrom
tests

Conversation

@toniher

@toniher toniher commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

This pull request adds a new end-to-end smoke test workflow for GGUF model inference, ensuring that the conda-built package can load, tokenize, run inference, and (optionally) generate embeddings using a small test model. The workflow builds the package, installs it in a fresh environment, downloads a sample GGUF model, and runs a new Python test script to verify core functionality.

New CI workflow for GGUF inference testing:

  • Added .github/workflows/test-gguf.yml to define a GitHub Actions workflow that builds the conda package, installs it in a clean environment, downloads a small GGUF model, and runs an end-to-end test to verify package and model functionality.

Test script for GGUF model validation:

  • Introduced test_gguf.py, a Python script that checks the ability to import the package, load a GGUF model, perform tokenization, run inference, and (optionally) generate embeddings, exiting with an error if any step fails.

Support tools used: Claude Code Opus 4.8, GitHub Copilot


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.

@conda-forge-webservices

Copy link
Copy Markdown
Contributor

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

It appears you are making a pull request from a branch in your feedstock and not a fork. This procedure will generate a separate build for each push to the branch and is thus not allowed. See our documentation for more details.

Please close this pull request and remake it from a fork of this feedstock.

Have a great day!

1 similar comment
@conda-forge-webservices

Copy link
Copy Markdown
Contributor

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

It appears you are making a pull request from a branch in your feedstock and not a fork. This procedure will generate a separate build for each push to the branch and is thus not allowed. See our documentation for more details.

Please close this pull request and remake it from a fork of this feedstock.

Have a great day!

@conda-forge-admin

Copy link
Copy Markdown
Contributor

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:

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

@toniher toniher closed this Jun 17, 2026
@jjerphan

Copy link
Copy Markdown
Member

FYI, pull requests have to be made from forks, not from branches upstream like here otherwise builds are published on conda-forge.

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.

3 participants