flake: setup deployment (create user)

[flake-investigator]

CI Run: https://github.com/coder/coder/actions/runs/30110740039
Failed Job: https://github.com/coder/coder/actions/runs/30110740039/job/89539430230 (test-e2e)
Failure date: 2026-07-24
Run attempt: 1

Commit under test:

• SHA: 591f35757463a15575117b2482d5438302a2378e
• Author: Garrett Delfosse
• Commit: coder/coder@591f357

Failure evidence:

[testsSetup] › e2e/setup/addUsersAndLicense.spec.ts:7:5 › setup deployment

Error: expect(locator).toBeVisible() failed
Locator: getByText(/created successfully/)
Expected: visible
Received: <element(s) not found>
Timeout: 5000ms

at site/e2e/helpers.ts:1358
await expect(page.getByText(/created successfully/)).toBeVisible();

Timeline from the complete job log:

• The template-admin user was created successfully and its Template Admin role was assigned.
• Setup then submitted the next fixture, user-admin (useradmin@coder.com).
• The Save click completed at 16:56:44.611Z, followed by networkidle at 16:56:44.683Z.
• No success navigation or toast followed; the assertion timed out at 16:56:49.619Z.
• The setup project failed, so the remaining 93 e2e tests did not run.

Error analysis / root cause assessment:

• Classification: flaky test / timing-sensitive setup flow.
• The failure is in the shared createUser helper while creating the second non-owner fixture (user-admin), not in the commit's release tooling changes.
• Unlike the successful first fixture, the second submission did not reach the expected success state within Playwright's 5-second assertion timeout.
• The complete Actions log does not include the user-create HTTP response body, so the exact transient backend/UI condition is unclear. The best current assessment is a timing-sensitive create-user form submission or success-state transition in e2e setup.
• No Go race detector warning, panic, OOM, process-kill, or resource-exhaustion indicator appears in the complete job log.

Assignment analysis:

git blame -L 6,32 site/e2e/setup/addUsersAndLicense.spec.ts
git blame -L 1312,1372 site/e2e/helpers.ts
git log --oneline -10 --follow site/e2e/setup/addUsersAndLicense.spec.ts
git log --oneline -10 --follow site/e2e/helpers.ts

• site/e2e/setup/addUsersAndLicense.spec.ts has no recent substantive setup-flow changes; the latest entries are import/service-account maintenance.
• The assertion at the failing helper line changed in commit 15a2bab1 (feat: migrate from <GlobalSnackbar /> to sonner) by Jake Howell, which migrated create-user success handling to the current /created successfully/ toast.
• Assigning to @jakehwll as the most recent non-trivial modifier of the exact success-state assertion. Ownership is somewhat uncertain because the missing HTTP response prevents distinguishing a toast race from a transient create-user API failure.

Duplicate search (coder/internal):

• "setup deployment" "created successfully"
• "addUsersAndLicense.spec.ts"
• "helpers.ts:1358" createUser
• "getByText(/created successfully/)"
• "user-admin" e2e
• recently closed issues since 2026-06-24 for created successfully, createUser, and Playwright setup

No matching issue was found. Related but different:

• flake: create user with password #1605 — create-user test failed during competing login navigation; fixed by 580ba19a, not this post-submit timeout.

Reproduction:

cd site
pnpm playwright:test --forbid-only --workers 1 --project=testsSetup --grep "setup deployment"

Repeated runs may be needed because the failure is intermittent. Inspect the create-user request/response and preserve the page error state when the success toast does not appear.

[linear-code]

ENG-3092