ci: name the interop interpreter instead of relying on $GITHUB_PATH

The workflow already installed h5py into /opt/interop and set CLAWHDF5_REQUIRE_INTEROP=1, but it reached the tests only by appending that venv to $GITHUB_PATH, which Gitea's runner does not reliably propagate into test subprocesses. If `python3` resolved to the system interpreter instead, every interop suite would skip. Setting CLAWHDF5_PYTHON outright removes the question: together with REQUIRE_INTEROP the suites either run or the build goes red. Verified both directions locally — with a venv the four suites run 94 tests green; with a bogus interpreter and REQUIRE_INTEROP=1 the facade and netCDF4 suites fail 22 tests rather than skipping. Also documents creating the local `.venv` that `ci-test.sh` detects. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
2026-09-20 04:55:09 -07:00
parent 105cf13347
commit e17ab0ceef
2 changed files with 15 additions and 1 deletions
@@ -499,6 +499,14 @@ cargo build -p clawhdf5-agent --features "agent,float16,accelerate,parallel,gpu"
 # Tests
 cargo test --workspace            # all 1,650+ tests
 cargo test -p clawhdf5-agent      # agent memory tests
+scripts/ci-test.sh                # what CI runs: fmt, clippy matrix, tests,
+                                  # h5py/netCDF4 interop, no_std
+
+# The interop suites need a Python with h5py; on a PEP 668 system that has to
+# be a virtualenv. `ci-test.sh` finds `.venv` on its own, or set
+# CLAWHDF5_PYTHON. Without one they skip — set CLAWHDF5_REQUIRE_INTEROP=1 to
+# make that a failure instead.
+python3 -m venv .venv && .venv/bin/pip install h5py numpy netCDF4 xarray

 # Benchmarks
 cargo bench -p clawhdf5-agent               # agent memory suite