a73x/mux

Watch

e2e legibility: a scenario can die unnamed under set -eu #5

New issue

Open

opened 2026-08-13 06:34:33 +00:00 by a73x · 0 comments

a73x commented

2026-08-13 06:34:33 +00:00

(Migrated from git.a73x.sh)

M15 finding 7. When the failing pipeline is the mux client itself (e.g. sh being handed a socket path after a dispatch mutation), set -eu kills e2e.sh before the script reaches its own grep and e2e FAIL line — the run dies with sh's stderr and no scenario name. Observed live during Task 6's regrade-premise failure. The suite's catches are only legible when the failure reaches an assertion; the pipeline-death path bypasses them all. Wants a trap or per-scenario wrapper that names the scenario on ANY nonzero exit, not just assertion failures. See decisions.md M15.

Migrated from git-collab issue 97965f0ded2e19624d2879410f3a1fb7fd0db3ee.

Original author: a73x dev@a73x.sh.

M15 finding 7. When the failing pipeline is the mux client itself (e.g. sh being handed a socket path after a dispatch mutation), set -eu kills e2e.sh before the script reaches its own grep and e2e FAIL line — the run dies with sh's stderr and no scenario name. Observed live during Task 6's regrade-premise failure. The suite's catches are only legible when the failure reaches an assertion; the pipeline-death path bypasses them all. Wants a trap or per-scenario wrapper that names the scenario on ANY nonzero exit, not just assertion failures. See decisions.md M15. --- Migrated from git-collab issue `97965f0ded2e19624d2879410f3a1fb7fd0db3ee`. Original author: a73x <dev@a73x.sh>.

Sign in to join this conversation.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

a73x/mux#5

No description provided.