Skip to content

ci(carl-smoke): bump CARL_CHAT_TIMEOUT_SEC 90s→300s — unblock #1035 canary→main#1036

Merged
joelteply merged 1 commit into
canaryfrom
fix/smoke-chat-timeout-300s
May 4, 2026
Merged

ci(carl-smoke): bump CARL_CHAT_TIMEOUT_SEC 90s→300s — unblock #1035 canary→main#1036
joelteply merged 1 commit into
canaryfrom
fix/smoke-chat-timeout-300s

Conversation

@joelteply
Copy link
Copy Markdown
Contributor

Summary

Closes the canary→main blocker (#1035). Smoke was failing with ❌ chat probe: no AI reply within 90s on ubuntu-latest CI (no GPU = CPU cold-load > 90s).

Fix

Workflow env: CARL_CHAT_TIMEOUT_SEC: '300'. Doesn't change pass criteria — still requires real persona reply.

🤖 Generated with Claude Code

Carl-install smoke was failing with no-AI-reply-within-90s on ubuntu-latest CI runners (no GPU passthrough → CPU cold-load exceeds 90s). Doesn't change pass criteria; just gives CI realistic headroom.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@joelteply
Copy link
Copy Markdown
Contributor Author

LGTM from codex-b741.

4-line workflow change, env-override only, doesn't relax pass criteria — just gives the cold-CPU-load enough wall-time to actually finish first inference. Same shape as the existing CARL_HEALTH_TIMEOUT_SEC=300 just below it (model-init cold pull pattern).

Justification is correct: ubuntu-latest CI runners have no GPU passthrough by design (Joel's no-CPU-fallback rule means continuum-core panics → workaround is CPU inference via DMR which is slow). 300s is conservative — chat-probe locally on Mac Metal completes in ~30s, so 10x margin for CPU CI.

Once green, #1035 canary→main unblocks. Carl-from-cambriantech.github.io install gets all 18 fixes.

Safe to merge to canary.

@joelteply joelteply merged commit ea01d64 into canary May 4, 2026
2 of 3 checks passed
@joelteply joelteply deleted the fix/smoke-chat-timeout-300s branch May 4, 2026 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant