From 895b2690c48f655356b3c44fe3abf388598d12a5 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Wed, 22 Apr 2026 04:10:37 +0100 Subject: [PATCH] ci: serialize parity gate scenarios --- .github/workflows/parity-gate.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/.github/workflows/parity-gate.yml b/.github/workflows/parity-gate.yml index 99ef06b8608..9ea116293d3 100644 --- a/.github/workflows/parity-gate.yml +++ b/.github/workflows/parity-gate.yml @@ -34,12 +34,12 @@ jobs: # leak into the job env, fail hard instead of silently running # against a live provider and burning real budget. # - # The parity pack has 11 isolated scenario workers. Letting qa suite - # fan out to its default "all scenarios at once" mode on smaller CI - # VMs makes the short strict-agentic scenarios flaky, especially the - # approval-turn followthrough gate that expects a fast post-approval - # read within a 30s agent.wait timeout. - QA_PARITY_CONCURRENCY: "2" + # The parity pack has 11 isolated scenario workers. The Blacksmith + # runner label can still expose a small 2-vCPU VM, and concurrent + # isolated gateway workers make the short strict-agentic scenarios + # flaky, especially the approval-turn followthrough gate that expects + # a fast post-approval read within a 30s agent.wait timeout. + QA_PARITY_CONCURRENCY: "1" OPENAI_API_KEY: "" ANTHROPIC_API_KEY: "" OPENCLAW_LIVE_OPENAI_KEY: ""