Skip to content

test(e2e): first-run covers three isolated benches from /new (CL-9507) - #1038

Merged
TheGreatAxios merged 4 commits into
mainfrom
cl-9507-new-bench-e2e
Sep 30, 2026
Merged

TheGreatAxios merged 4 commits into
mainfrom
cl-9507-new-bench-e2e

Conversation

@TheGreatAxios

Copy link
Copy Markdown
Contributor

One browser e2e creates three benches from /new with different opening messages and asserts: three child tenants under the workspace (stock tenants routes), one agent definition deployed per bench, three sidebar bench rows with short titles plus a Workers group, and no cross-bench leakage of opening messages.

Self-naming is not covered: the harness has no scripted/noop inference path (no E2E_PROVIDER wiring under e2e/ or apps/hub).

Resolves CL-9507

@linear-code

linear-code Bot commented Sep 30, 2026 •

Copy link
Copy Markdown

CL-9507

CL-9620

@TheGreatAxios TheGreatAxios changed the title test(e2e): three benches from /new stay isolated child tenants (CL-9507) test(e2e): first-run covers three isolated benches from /new (CL-9507) Sep 30, 2026
A hub left running keeps reconciling the shared database, and fails the
deployment allocations of any hub booted after it in the same process with
provisioner_unavailable. That ended the first run's Myra before the flow
returned to /new, which sent the page back to /onboarding.
@TheGreatAxios
TheGreatAxios merged commit db3c83d into main Sep 30, 2026
3 checks passed
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