Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS
JavaScript ai-agentsdashboarddeveloper-toolsdigital-twinquantified-selfsecond-brainself-hostedtailscale
fix: warm Chrome on client CI runners before browser fixtures
Adam Eivy17548e9d36a3
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.ymlindex 5f0bae3fbf..df7c74886b 100644--- a/.github/workflows/ci.yml+++ b/.github/workflows/ci.yml@@ -402,6 +402,14 @@ jobs:vitest-client-${{ runner.os }}-${{ hashFiles('client/package-lock.json') }}-vitest-client-${{ runner.os }}-+ # These runners have their own page cache: the DB job's warm-up cannot+ # help client fixtures (#9641). Apply the same bounded mitigation here+ # and retain its duration alongside the fixtures' existing phase timings.+ # A passing launch is a non-reproduction, not proof of the startup cause.+ - name: Warm the Chrome install for client fixtures+ if: needs.impact.outputs.client_mode != 'skip'+ run: bash scripts/ci-warm-test-chrome.sh+- name: Run client testsif: needs.impact.outputs.client_mode != 'skip'env: