Issue #1: set up one Actions workflow with a custom Docker image #3

Merged
marmaduke merged 3 commits from issue/1-set-up-one-actions-workflow-with-a-custo into ins-local 2026-09-25 14:46:02 +02:00
Owner

Summary

Adds a single GitHub Actions workflow that builds a custom Docker image and runs the pytest base test suite.

Changes

  • Dockerfile.test — custom image based on python:3.11-slim with CPU-only PyTorch, numpy, safetensors, and pytest. CPU-only torch keeps the image small (~200 MB vs ~2 GB) since the Python test suites (artifact framing, converter recipes, bench/serve corpus) exercise host-side logic only.
  • .github/workflows/ci.yml — one workflow (pytest-base) that builds Dockerfile.test and runs the pytest base suite. Triggers on push and PR to the default branch.

How to test

docker build -f Dockerfile.test -t ninfer-test:ci .
docker run --rm ninfer-test:ci

Or locally without Docker:

python3 -m pytest tests/artifact tests/convert tests/test_bench_matrix.py tests/test_serve_corpus.py

The entrypoint in Dockerfile.test already targets the correct test paths, so docker run --rm ninfer-test:ci runs the full suite with no extra arguments.

## Summary Adds a single GitHub Actions workflow that builds a custom Docker image and runs the pytest base test suite. ## Changes - **`Dockerfile.test`** — custom image based on `python:3.11-slim` with CPU-only PyTorch, numpy, safetensors, and pytest. CPU-only torch keeps the image small (~200 MB vs ~2 GB) since the Python test suites (artifact framing, converter recipes, bench/serve corpus) exercise host-side logic only. - **`.github/workflows/ci.yml`** — one workflow (`pytest-base`) that builds `Dockerfile.test` and runs the pytest base suite. Triggers on push and PR to the default branch. ## How to test ```bash docker build -f Dockerfile.test -t ninfer-test:ci . docker run --rm ninfer-test:ci ``` Or locally without Docker: ```bash python3 -m pytest tests/artifact tests/convert tests/test_bench_matrix.py tests/test_serve_corpus.py ``` The entrypoint in `Dockerfile.test` already targets the correct test paths, so `docker run --rm ninfer-test:ci` runs the full suite with no extra arguments.
- Add Dockerfile.test: Python 3.11 image with CPU-only torch, numpy,
  safetensors, and pytest for running the pytest base test suite
  (artifact, convert, bench_matrix, serve_corpus) in CI.
- Add .github/workflows/ci.yml: single workflow that builds the
  custom image and runs the pytest base suite on push/PR to main.
marmaduke force-pushed issue/1-set-up-one-actions-workflow-with-a-custo from 42b5dd1bdc to 1e7bd3a0c4
Some checks failed
ci / pytest-base (pull_request) Failing after 4s
2026-09-25 14:29:31 +02:00
Compare
issue/1: fix CI failure
Some checks failed
ci / pytest-base (pull_request) Failing after 5s
5cb9c54a00
issue/1: fix CI failure
All checks were successful
ci / pytest-base (pull_request) Successful in 2m1s
438a9ce1c9
marmaduke merged commit 449c89e943 into ins-local 2026-09-25 14:46:02 +02:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
marmaduke/ninfer-4090!3
No description provided.