test: keep scoped memory fixtures fresh#126
Conversation
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
Greptile SummaryKeeps scoped-memory test fixtures above the confidence-decay threshold by assigning both scoped and global memories the test setup’s current timestamp.
Confidence Score: 5/5The PR appears safe to merge, with both test-only changes directly addressing time-dependent fixture decay. The changed timestamps preserve the tests’ intended scoped-memory eligibility while leaving production behavior and asserted ranking semantics unchanged.
|
| Filename | Overview |
|---|---|
| tests/search-health-scope.test.ts | Replaces aging fixed memory dates with a shared setup-time timestamp, preventing unrelated confidence filtering from destabilizing health and scope assertions. |
| tests/search-scoped-memory.test.ts | Keeps scoped-memory fixtures fresh so the test continues exercising scope-based ranking rather than fixture-age decay. |
Reviews (1): Last reviewed commit: "test: keep scoped memory fixtures fresh" | Re-trigger Greptile
Summary
Keep the scoped-memory test fixtures fresh so confidence decay does not filter the expected scoped memory before the ranking assertion runs.
Root cause
The fixtures used a fixed April 2026 timestamp. As time passed, decay dropped the scoped memory below the compact-mode confidence threshold, causing two unrelated ranking tests to fail.
Verification
pnpm run buildpnpm test -- tests/search-health-scope.test.ts tests/search-scoped-memory.test.tspnpm test— 612 passed