Skip to content

✅ test: Fixing retention test for update operations#137

Merged
s-b-e-n-s-o-n merged 1 commit intoCodesWhat:mainfrom
Waler:bugfix/test_retention_update_operation_store
Mar 12, 2026
Merged

✅ test: Fixing retention test for update operations#137
s-b-e-n-s-o-n merged 1 commit intoCodesWhat:mainfrom
Waler:bugfix/test_retention_update_operation_store

Conversation

@Waler
Copy link
Contributor

@Waler Waler commented Mar 11, 2026

The test failed because the wrong 2 operations where left in the store after prune.
Reason: The 97 test updates on the third operation were executed with a timestamp earlier than the original operation timestamp. Therefore the third operation was defined as the oldest (by updatetime) of the three operations and pruned.

@vercel
Copy link

vercel bot commented Mar 11, 2026

@Waler is attempting to deploy a commit to the CodesWhat Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

@s-b-e-n-s-o-n s-b-e-n-s-o-n left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clean fix — the original timestamps used local-time February dates that could land before the UTC insertion timestamps depending on timezone, causing retention pruning to pick the wrong operations. Bumping to March makes the update timestamps unambiguously newer. Tests pass. Thanks @Waler!

@codecov
Copy link

codecov bot commented Mar 12, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@s-b-e-n-s-o-n s-b-e-n-s-o-n merged commit d6bea15 into CodesWhat:main Mar 12, 2026
14 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants