Mark upstream umap test as flaky - #8107
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughAdds one UMAP test selector to the flaky upstream xfail list and relaxes an absolute-tolerance in a nearest-neighbors pickle test for ChangesTest changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Comment |
This fails sometimes with a trustworthiness score _just_ below 0.85 (e.g. 0.844).
b8ba314 to
8120597
Compare
|
/merge |
1 similar comment
|
/merge |
This fails sometimes with a trustworthiness score just below 0.85 (e.g. 0.844). This was marked as flaky before #8073 removed it, but it's still flaky so we add it back.