Restore venv activation in test step, clear VPS cache

Cached venv has broken internal paths even when using venv/bin/python directly. Clear caches and use . venv/bin/activate + python -m pytest which correctly sets VIRTUAL_ENV for module resolution. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
fix(ci): use explicit venv/bin/python instead of activate+python3
2026-06-04 11:07:23 +08:00 · 2026-06-04 10:59:55 +08:00
1 changed files with 1 additions and 1 deletions
@@ -89,7 +89,7 @@ jobs:
        run: |
          cd dashboard/backend
          . venv/bin/activate
-          python3 -m pytest tests/ -v --timeout=60 \
+          python -m pytest tests/ -v --timeout=60 \
            --cov=. --cov-report=xml --cov-report=term \
            --junit-xml=test-results.xml \
            --cov-fail-under=49
Author	SHA1	Message	Date
Gan, Jimmy	56fd761618	Restore venv activation in test step, clear VPS cache Cached venv has broken internal paths even when using venv/bin/python directly. Clear caches and use . venv/bin/activate + python -m pytest which correctly sets VIRTUAL_ENV for module resolution. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 11:07:23 +08:00
Gan, Jimmy	3989e281c0	fix(ci): use explicit venv/bin/python instead of activate+python3 Deploy Dashboard (Main) / Deploy to Production (push) Has been cancelled Details Deploy Dashboard (Main) / Frontend Tests (push) Has been cancelled Details Deploy Dashboard (Main) / Backend Tests (push) Has been cancelled Details activate doesn't reliably shadow system python3 on the VPS runner. Using the explicit venv path matches what the cache validation check already uses. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 10:59:55 +08:00