From 3196edde85ed7f4a909c3a627af75b47593c7f5e Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 2 Sep 2026 00:50:09 +0000 Subject: [PATCH] fix(strix): remove the 300s LLM_TIMEOUT cap, matching the sibling zero-timeout env vars MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit strix.yml already sets STRIX_MEMORY_COMPRESSOR_TIMEOUT=0, STRIX_PROCESS_TIMEOUT_SECONDS=0, and STRIX_TOTAL_TIMEOUT_SECONDS=0 right next to LLM_TIMEOUT, and the job's own concurrency-block comment says inference "has no wall-clock deadline" and central scans "may take more than two hours per model" per docs/product-goal-directive.md §8 (no uniform LLM timeout ceiling; default unlimited). LLM_TIMEOUT was still hardcoded to 300 seconds, contradicting both the neighboring env vars and that documented intent. scripts/ci/test_strix_quick_gate.sh already asserts `export LLM_TIMEOUT=0` (line 302) and fails on origin/main today because of this exact mismatch — confirmed directly against origin/main (fb02129, .github/workflows/strix.yml:786) before this fix, independent of any single PR's diff. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_019YgmaEKnPhrsbSyQBierFH --- .github/workflows/strix.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/strix.yml b/.github/workflows/strix.yml index 7674b3040f..8c742a10a0 100644 --- a/.github/workflows/strix.yml +++ b/.github/workflows/strix.yml @@ -783,7 +783,7 @@ jobs: PR_HEAD_SHA: ${{ github.event_name == 'pull_request_target' && github.event.pull_request.head.sha || github.event.client_payload.pr_head_sha }} IS_PR_EVIDENCE_RUN: ${{ (github.event_name == 'pull_request_target' || github.event.client_payload.pr_number != '') && 'true' || 'false' }} run: | - export LLM_TIMEOUT=300 + export LLM_TIMEOUT=0 export STRIX_MEMORY_COMPRESSOR_TIMEOUT=0 export STRIX_PROCESS_TIMEOUT_SECONDS=0 export STRIX_TOTAL_TIMEOUT_SECONDS=0