backend-deploy.yml test declares needs: build (L136 on main @ efa935c), so pytest does not start until the full multi-GB image build and GHCR push finish. On the PR run added in #364 that was ~2m6s of build before ~2m12s of tests.
deploy already declares needs: [build, test], so dropping needs: from test would not weaken the deploy gate — both must still pass. It only lets them run concurrently, roughly halving PR feedback time.
Trade-off to weigh: the current serialization saves runner minutes when the build is broken, since tests never start. Now that the suite gates PRs rather than only post-merge pushes, faster feedback is probably worth more than the saved minutes — but that is a judgment call, hence an issue rather than a patch.
backend-deploy.ymltestdeclaresneeds: build(L136 onmain@ efa935c), sopytestdoes not start until the full multi-GB image build and GHCR push finish. On the PR run added in #364 that was ~2m6s of build before ~2m12s of tests.deployalready declaresneeds: [build, test], so droppingneeds:fromtestwould not weaken the deploy gate — both must still pass. It only lets them run concurrently, roughly halving PR feedback time.Trade-off to weigh: the current serialization saves runner minutes when the build is broken, since tests never start. Now that the suite gates PRs rather than only post-merge pushes, faster feedback is probably worth more than the saved minutes — but that is a judgment call, hence an issue rather than a patch.