CI: run cultcache-py, cultcache-rs and GameCult.Caching.Tests on push and PR #87
Loading…
Reference in a new issue
No description provided.
Delete branch "libby/ci-cultcache-py-rs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The forge runs one Linux job on push and PR (cultmesh-portability) plus QUIC native. cultcache-ts is already tested there. These ran nowhere on the forge: cultcache-py unit tests (only in the dispatch-only Windows interop workflow), cultcache-rs, and tests/GameCult.Caching.Tests.
Three steps are added to the existing portability job instead of a new workflow, so the one-slot runner keeps one job and the existing concurrency group (cancel-in-progress on PR) covers them. The Python step follows the cultcache-ts step because one store-lock test needs the built TS cache.
Local timings (non-root): Python 176 tests OK, 1 skipped, 6 s; cargo test cultcache-rs OK (18 doctests), 22 s; Caching.Tests 1261 passed, 4 skipped, 44 s warm. Not yet run on the forge runner: this PR's own CI is the proof.
Still uncovered on push/PR: cultnet-py/rs and cultmesh-py/rs tests, Networking, Geometry and QUIC C# test projects, Kotlin (Windows dispatch job only or nowhere).
🤖 Generated with Claude Code
b6307889a0b36036942e