Skip to content

e2e: note that not every failed suite retains a namespace - #924

Open
Yuan Gao (ygao-g) wants to merge 1 commit into
agent-substrate:mainfrom
ygao-g:docs-e2e-namespace-retention
Open

e2e: note that not every failed suite retains a namespace#924
Yuan Gao (ygao-g) wants to merge 1 commit into
agent-substrate:mainfrom
ygao-g:docs-e2e-namespace-retention

Conversation

@ygao-g

Copy link
Copy Markdown
Collaborator

The "After a failure" section of internal/e2e/README.md tells you a failed run
keeps its namespaces so you can read the worker-pod logs. That only holds for
namespaces the suite created itself. A suite that runs against a pre-installed
worker pool keeps its atespace in Valkey, not Kubernetes, so a failure leaves
nothing labeled ate.dev/e2e and the documented recovery step comes up empty.

Adds a short caveat naming TestActorEgress as the case in the tree and pointing
at the standing ate-demo-egress namespace instead. Docs only.

The "After a failure" section promises a kept namespace, but retention only
covers namespaces the suite created. A suite running against a pre-installed
worker pool holds its atespace in Valkey and leaves nothing labeled
ate.dev/e2e behind, so point the reader at the standing demo namespace.
@ygao-g
Yuan Gao (ygao-g) marked this pull request as ready for review August 13, 2026 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant