jimmy/nas-tools
1
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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>
This commit is contained in:
Gan, Jimmy
2026-06-04 10:59:55 +08:00
parent 90546b6c9a
commit 3989e281c0
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/deploy.yml
+1 -2
View File
@@ -88,8 +88,7 @@ jobs:
- name: Run tests with coverage - name: Run tests with coverage
run: | run: |
cd dashboard/backend cd dashboard/backend
. venv/bin/activate venv/bin/python -m pytest tests/ -v --timeout=60 \
python3 -m pytest tests/ -v --timeout=60 \
--cov=. --cov-report=xml --cov-report=term \ --cov=. --cov-report=xml --cov-report=term \
--junit-xml=test-results.xml \ --junit-xml=test-results.xml \
--cov-fail-under=49 --cov-fail-under=49