From d29c2c3a13bf3e026209f69cea891ad7781f8445 Mon Sep 17 00:00:00 2001 From: "Gan, Jimmy" Date: Wed, 3 Jun 2026 11:50:31 +0800 Subject: [PATCH] Validate cached venv by testing pytest, not just python binary The cached venv's python binary may work but tool symlinks (pytest, etc.) break when restored in a different environment. Test pytest specifically to catch this. Co-Authored-By: Claude Opus 4.8 --- .gitea/workflows/deploy.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitea/workflows/deploy.yml b/.gitea/workflows/deploy.yml index 34e15b5..0aa28a3 100644 --- a/.gitea/workflows/deploy.yml +++ b/.gitea/workflows/deploy.yml @@ -55,7 +55,7 @@ jobs: cd dashboard/backend if [ "${{ steps.cache-python.outputs.cache-hit }}" = "true" ]; then echo "Restoring venv from cache $CACHE_KEY..." - if cp -a $CACHE_DIR/venv . && [ -f venv/bin/activate ] && venv/bin/python -c "import sys; sys.exit(0)"; then + if cp -a $CACHE_DIR/venv . && [ -f venv/bin/activate ] && venv/bin/python -m pytest --version >/dev/null 2>&1; then echo "Cache restored successfully" else echo "Cache corrupted, installing fresh..."