Use python -m pytest instead of pytest binary in CI

Venv symlinks break when cache is used across different environments (VPS host vs NAS Docker). python -m pytest is resilient because it loads pytest as a module, not via a shebang-based script. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
fix(ci): use Docker bridge gateway IP 172.21.0.1:3300 for checkout
2026-06-04 10:00:24 +08:00 · 2026-06-04 10:00:12 +08:00 · 2026-06-04 09:58:23 +08:00 · 2026-06-04 09:57:56 +08:00 · 2026-06-04 09:53:07 +08:00 · 2026-06-04 09:50:36 +08:00
3 changed files with 5 additions and 3 deletions
@@ -22,7 +22,7 @@ jobs:
      - name: Checkout repository
        run: |
          if [ ! -d .git ]; then
-            git clone --branch "${GITHUB_REF_NAME}" --depth=1 "http://172.21.0.4:3000/${GITHUB_REPOSITORY}.git" .
+            git clone --branch "${GITHUB_REF_NAME}" --depth=1 "http://172.21.0.1:3300/${GITHUB_REPOSITORY}.git" .
          fi

      - name: Resolve image tags
@@ -89,7 +89,7 @@ jobs:
        run: |
          cd dashboard/backend
          . venv/bin/activate
-          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
@@ -242,7 +242,9 @@ jobs:
          fi

      - name: Sync runtime compose file
-        run: cp dashboard/docker-compose.yml /nas-dashboard/docker-compose.yml
+        run: |
+          mkdir -p /nas-dashboard
+          cp dashboard/docker-compose.yml /nas-dashboard/docker-compose.yml

      - name: Deploy and verify
        run: |
Author	SHA1	Message	Date
Gan, Jimmy	00364114d5	Use python -m pytest instead of pytest binary in CI Venv symlinks break when cache is used across different environments (VPS host vs NAS Docker). python -m pytest is resilient because it loads pytest as a module, not via a shebang-based script. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 10:00:24 +08:00
Gan, Jimmy	e3ac6344f6	fix(ci): use Docker bridge gateway IP 172.21.0.1:3300 for checkout Deploy Claude Dev (Dev) / deploy-claude-dev-dev (push) Failing after 1m4s Details host.docker.internal not resolving in act containers on Synology Docker. The gateway IP 172.21.0.1 routes to the host where Gitea is now bound to 0.0.0.0:3300. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 10:00:12 +08:00
Gan, Jimmy	92c1f29843	Merge main into dev: resolve CI checkout URL conflict Deploy Claude Dev (Dev) / deploy-claude-dev-dev (push) Failing after 25s Details Use host.docker.internal:3300 with ubuntu-latest runner. Gitea port now bound to 0.0.0.0:3300 so Docker containers can reach it. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 09:58:23 +08:00
Gan, Jimmy	d42a5422db	chore: trigger claude-dev CI pipeline	2026-06-04 09:57:56 +08:00
Gan, Jimmy	85ca387877	fix(ci): use host.docker.internal:3300 for checkout after Gitea port fix Changed Gitea HTTP port binding from 127.0.0.1:3300 to 0.0.0.0:3300 so Docker containers can reach Gitea via host.docker.internal. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 09:53:07 +08:00
Gan, Jimmy	bb9a4c3977	Create /nas-dashboard directory before syncing compose file Docker volume mounts may not auto-create mount points inside the job container. Use mkdir -p to ensure the target directory exists before copying files. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 09:50:36 +08:00
Gan, Jimmy	761f5f562b	fix(ci): use nas:host runner with localhost:3300 for claude-dev CI Deploy Claude Dev (Dev) / deploy-claude-dev-dev (push) Has been cancelled Details The act Docker containers on the NAS runner cannot reach Gitea on the gitea_gitea network despite the runner config. Switching to the 'nas' runner label which uses host mode — jobs run directly on the NAS host where localhost:3300 reaches Gitea. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-04 09:49:30 +08:00