Skip to content

Aged-profile startup e2e: CI only ever boots pristine profiles #994

Description

@jonathanKingston

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area:ciContinuous integration and test infrastructurearea:performancePerformance, resource usage, and package sizearea:storagePersistence, threads, memories, and migrationenhancementNew feature or requestpriority:p2Important issue to address soon

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions