fix(e2e): emit full diagnose JSON burst on EIC smoke failure (#767) #2346
Reference in New Issue
Block a user
Delete Branch "fix/e2e-smoke-diagnose-detail-767"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
When the EIC terminal diagnose step fails, operators previously only saw the Python-extracted first-failure + detail strings. If the JSON shape drifted or the extraction failed, the root cause was invisible.
Changes
Verification
bash -nSOP Checklist
Comprehensive testing performed
N/A — shell-script logging change; no functional logic modified. Verified syntax with
bash -n.Local-postgres E2E run
N/A — e2e shell script change, not backend code.
Staging-smoke verified or pending
This change improves the diagnostic surface of the staging-smoke script itself.
Root-cause not symptom
N/A — diagnostic-improvement change.
Five-Axis review walked
No backwards-compat shim / dead code added
N/A — no code shims.
Memory/saved-feedback consulted
N/A — straightforward diagnostic logging improvement.
Related
Review on current head
2f53bbac6c.Scope note: this is not strictly shell-only; it includes the requested shell diagnostic logging change in tests/e2e/test_staging_full_saas.sh plus a docs-only backend-contract status update in docs/architecture/backends.md. Both are non-product-behavior changes.
Correctness: on terminal EIC smoke diagnose failure, the script now emits the full diagnose JSON burst bracketed for CI logs before the existing failure, so operators can inspect every step/detail even if compact Python extraction fails or the JSON shape drifts. Robustness improves diagnostics without altering pass/fail criteria. Security: no new secrets are generated or persisted; this echoes the existing diagnostic payload already fetched by the test, so no new auth surface. Performance impact is only on failure path. Readability is clear and grep-friendly.
Required contexts are green and mergeable=true.
Official APPROVED on current head. Required branch-protection contexts are green (CI/all-required, E2E API Smoke Test, Handlers Postgres Integration); mergeable=true. Governance reds are non-required pre-#2331. Diff is e2e diagnostic JSON emission only.
merge-queue: updated this branch with
mainatbe1f38b7b5a5. Waiting for CI on the refreshed head.APPROVED on current head
b057994cac.Fresh re-review after branch update. The current PR files/diff API returns no changed files against the current base, so the original diagnose-JSON change has no additional delta on this head; the head is a merge-from-main update of the prior approved head. 5-axis: correctness/robustness/security/performance/readability unchanged from prior approval; no new product, auth, secret, or destructive path is introduced by the current PR diff.
Required CI is green on this head (
CI / all-required, E2E API Smoke, Secret scan, lint-required-no-paths); mergeable=true; merge-queue label is present.Fresh approval on current head
b057994c. CR2 approval is current-head, required core contexts are green, mergeable=true, and the head is merge-from-main only with no product delta. Approving for merge queue.