-
Notifications
You must be signed in to change notification settings - Fork 3
Aged-profile startup e2e: CI only ever boots pristine profiles #994
Copy link
Copy link
Open
Labels
area:ciContinuous integration and test infrastructureContinuous integration and test infrastructurearea:performancePerformance, resource usage, and package sizePerformance, resource usage, and package sizearea:storagePersistence, threads, memories, and migrationPersistence, threads, memories, and migrationenhancementNew feature or requestNew feature or requestpriority:p2Important issue to address soonImportant issue to address soon
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
area:ciContinuous integration and test infrastructureContinuous integration and test infrastructurearea:performancePerformance, resource usage, and package sizePerformance, resource usage, and package sizearea:storagePersistence, threads, memories, and migrationPersistence, threads, memories, and migrationenhancementNew feature or requestNew feature or requestpriority:p2Important issue to address soonImportant issue to address soon
Both startup defects fixed in #988 were invisible in CI because e2e always boots a pristine profile. The failure class is
call-frequency × per-call-cost × data-size— and CI has all three near zero.Add one startup e2e seeded with a worn fixture: multi-MB config.json (dummy llm-history), a workspace with a few thousand files, hundreds of gitignored dirs (e.g. generated
.wdio-*-style names), several tracked projects. Assert time-to-interactive under a threshold and that no Copse process exceeds a memory ceiling during the smoke window.