test: stop rebuilding folderInfo() across clock ticks in listingCache tests#27
Merged
Conversation
… tests The helper stamps lastModified with Date.now(), so comparing a cached object against a second, freshly built folderInfo(n) only passes while both calls land in the same millisecond. On a loaded CI runner the tick in between is likely — PR #22's check hit exactly this on the invalidateConnection test. Both comparison sites now build the object once and assert against that same reference. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdated listing cache unit tests to avoid time-dependent ChangesListing cache test stability
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
folderInfo(n)test helper stampslastModified: Date.now(), so any assertion that compares a cached object against a second, freshly builtfolderInfo(n)only passes while both calls land in the same millisecond. On a loaded CI runner the clock ticking in between is likely — PR #22'scheckrun just failed exactly there (invalidateConnectiontest, line 196, a one-linelastModifieddiff), while the same suite passes locally every time.Both comparison sites (the inflight-dedupe test and the
invalidateConnectiontest) now build the object once and assert against the same reference.Third and hopefully last of today's test-flake fixes, after #25 and #26.
🤖 Generated with Claude Code
Summary by CodeRabbit