fix(infra): ensure E2E suite setup initializes database before CLI commands #1177

Merged

freemo merged 1 commits from fix/e2e-auto-init into master

2026-04-03 02:06:59 +00:00

Author	SHA1	Message	Date
brent.edwards	998aaf25f8	fix(infra): ensure E2E suite setup initializes database before CLI commands CI / benchmark-publish (pull_request) Has been skipped Details CI / lint (pull_request) Failing after 27s Details CI / quality (pull_request) Successful in 46s Details CI / security (pull_request) Failing after 47s Details CI / typecheck (pull_request) Failing after 51s Details CI / coverage (pull_request) Has been skipped Details CI / benchmark-regression (pull_request) Has been skipped Details CI / build (pull_request) Successful in 27s Details CI / helm (pull_request) Successful in 29s Details CI / unit_tests (pull_request) Failing after 2m13s Details CI / docker (pull_request) Has been skipped Details CI / e2e_tests (pull_request) Failing after 14m25s Details CI / integration_tests (pull_request) Failing after 22m27s Details CI / status-check (pull_request) Failing after 1s Details Centralize E2E initialization in common suite setup so DB-dependent CLI commands no longer rely on per-suite or per-test init workarounds. This also sanitizes suite-home names to prevent invalid path-derived initialization failures in isolated Robot runs. ISSUES CLOSED: #1023	2026-04-03 01:43:27 +00:00