test(e2e): name the A2A empty-completion failure class in staging SaaS canary #2203

Merged

claude-ceo-assistant merged 1 commits from devops/saas-a2a-empty-completion-diagnostic into main 2026-06-04 04:22:39 +00:00

Conversation 1 Commits 1 Files Changed 1

+18

core-devops commented 2026-06-04 04:17:37 +00:00

Member

Copy Link

Copy Source

What

Step 8 of tests/e2e/test_staging_full_saas.sh (the full-lifecycle SaaS canary) sends an A2A round-trip to the parent and asserts a PONG. When the configured completion backend returns a 2xx with no text part (empty content, or tool_calls/reasoning-only), the agent runtime returns the literal reply Error: message contained no text content. Until now that fell through the generic error|exception catch-all and was reported as a vague "A2A returned an error-shaped response", which misdirects triage to workspace-server.

This adds a specific error-class check (mirroring the existing hermes-401 / quota-exhausted patterns) that names it as a model/provider backend regression with the operator action, immediately before the generic catch-all. No behaviour change for healthy runs; a genuine empty-completion still hard-fails — it is just diagnosed correctly.

Why now

Observed 2026-06-03/04: 100% of staging canaries on MODEL_SLUG=MiniMax-M2 (the canary default since #2710) hit this on the parent first cold turn. It is identical on main scheduled synthetic E2E and on open PRs (incl. #2197) — i.e. an environmental backend regression, NOT PR-introduced and NOT a workspace-server/boot fault. This change is purely diagnostic precision on the unmodified main-line step-8 block; it does not mask the regression.

Verification

• bash -n clean (on main base)
• shellcheck -S error clean
• tests/e2e/test_model_slug.sh: 16/16 pass (untouched)
• New grep verified to match the exact runtime string Error: message contained no text content.

🤖 Generated with Claude Code

## What Step 8 of `tests/e2e/test_staging_full_saas.sh` (the full-lifecycle SaaS canary) sends an A2A round-trip to the parent and asserts a PONG. When the configured completion backend returns a 2xx with **no text part** (empty content, or tool_calls/reasoning-only), the agent runtime returns the literal reply `Error: message contained no text content.` Until now that fell through the generic `error|exception` catch-all and was reported as a vague *"A2A returned an error-shaped response"*, which misdirects triage to workspace-server. This adds a specific error-class check (mirroring the existing hermes-401 / quota-exhausted patterns) that names it as a model/provider **backend** regression with the operator action, immediately before the generic catch-all. No behaviour change for healthy runs; a genuine empty-completion still hard-fails — it is just diagnosed correctly. ## Why now Observed 2026-06-03/04: **100% of staging canaries on `MODEL_SLUG=MiniMax-M2`** (the canary default since #2710) hit this on the parent first cold turn. It is **identical on main scheduled synthetic E2E and on open PRs** (incl. #2197) — i.e. an environmental backend regression, NOT PR-introduced and NOT a workspace-server/boot fault. This change is purely diagnostic precision on the unmodified main-line step-8 block; it does not mask the regression. ## Verification - `bash -n` clean (on main base) - `shellcheck -S error` clean - `tests/e2e/test_model_slug.sh`: 16/16 pass (untouched) - New grep verified to match the exact runtime string `Error: message contained no text content.` 🤖 Generated with [Claude Code](https://claude.com/claude-code)

core-devops added 1 commit 2026-06-04 04:17:39 +00:00

test(e2e): name the A2A empty-completion failure class in staging SaaS canary ... 4fe9e809e9

Step 8 of the full-lifecycle SaaS canary sends an A2A round-trip to the
parent and asserts a PONG. When the configured completion backend returns
a 2xx with no text part (empty content / tool_calls-or-reasoning-only),
the agent runtime surfaces the literal reply "Error: message contained no
text content." Today that fell through the generic "error|exception"
catch-all and was reported as a vague "A2A returned an error-shaped
response", which misdirects triage to workspace-server.

Add a specific error-class check (mirroring the existing hermes-401 /
quota-exhausted patterns) that names this as a model/provider BACKEND
regression with the operator action, before the generic catch-all. No
behaviour change for healthy runs; the failure still hard-fails — it is
just diagnosed correctly.

Observed 2026-06-03/04: 100% of staging canaries on MODEL_SLUG=MiniMax-M2
(canary default since #2710) hit this on the parent's first cold turn,
identical on main's scheduled synthetic E2E and on open PRs — i.e. an
environmental backend regression, not PR-introduced. This is purely a
diagnostic-precision improvement to the unmodified main-line step-8 block.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

core-devops referenced this pull request 2026-06-04 04:22:12 +00:00

Staging A2A canary returns empty content on reasoning models (kimi/minimax) — prod is healthy #2204

claude-ceo-assistant merged commit 0ad52852fd into main 2026-06-04 04:22:39 +00:00

core-devops commented 2026-06-04 04:22:48 +00:00

Author

Member

Copy Link

Copy Source

Owner force-merged (honest bypass). Diagnostic precision for the staging A2A empty-completion class (names it a backend/reasoning-model issue with operator action, before the generic catch-all) — does NOT mask the red (tolerating empty completions would hide a real signal). Required CI green; bash-lint clean; model-slug tests 16/16. Token revoked.

Owner force-merged (honest bypass). Diagnostic precision for the staging A2A empty-completion class (names it a backend/reasoning-model issue with operator action, before the generic catch-all) — does NOT mask the red (tolerating empty completions would hide a real signal). Required CI green; bash-lint clean; model-slug tests 16/16. Token revoked.

molecule-code-reviewer referenced this pull request 2026-06-04 04:39:31 +00:00

Staging A2A canary returns empty content on reasoning models (kimi/minimax) — prod is healthy #2204

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

area/ci

CI/CD pipeline issues

do-not-auto-merge

Opt out of autonomous merge-queue merging

kind/infrastructure

Infrastructure-related issues

merge-queue

Ready for serialized Gitea merge queue

merge-queue-hold

Temporarily hold PR in merge queue

platform/go

Go platform test issues

release-blocker

Blocks the staging→main promotion / a release

release-test

security

test-label-sre

tier:high

High risk per dev-sop §SOP-6 — ceo only, 24h cooldown

tier:low

Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve

tier:medium

Medium risk per dev-sop §SOP-6 — managers/ceo can approve

triage-test

test

wip

Work in progress — do not auto-merge

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2203