fix(tests): align 3 stale OSS test assertions with intentional defaults#164
Conversation
|
Warning Review limit reached
More reviews will be available in 25 minutes and 31 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughFive small, independent edits: ChangesMiscellaneous Fixes and Test Alignment
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
…rmat Three OSS test failures were stale assertions that lagged intentional behavior changes on main; fix the tests (the application behavior is correct): - test_unified_search_floor: RetrievalFloorConfig.enabled default flipped True->False, so the floor-applied test must opt in with enabled=True. - test_litellm_client::test_config_defaults: max_retries default is now 3 (native litellm num_retries adoption, #124), not 1. - test_embedding_service_concurrency: model inference is now serialized by _MODEL_ENCODE_LOCK (#153, fixes a tensor race), so recorder.peak is always 1; the old `peak >= 2` assertion contradicted the new design. Also applies pre-existing ruff-format drift to billing_meter.py and extraction/outcome.py (formatting only, no behavior change).
7eda9b5 to
49cb14d
Compare
Summary
Nightly
/check-and-testrun found 3 OSS unit-test failures that were stale assertions lagging intentional behavior changes on main. The application code is correct; the tests are fixed to match.test_unified_search_floor::test_floor_applied_per_armRetrievalFloorConfig(user_playbook_floor=-5.0)enabled=Trueenableddefault flippedTrue→False; the floor-applied test must opt in.test_litellm_client::test_config_defaultsmax_retries == 1max_retries == 3num_retries; default is now 3.test_embedding_service_concurrency::test_embed_texts_caps_and_queuespeak >= 2peak == 1_MODEL_ENCODE_LOCKserializing inference (tensor-race fix); encode peak is always 1.Also includes pre-existing ruff-format drift in
billing_meter.pyandextraction/outcome.py(formatting only).Verification
Full OSS unit + integration suite: 3061 passed, 0 failed (
pytest tests/ --ignore=tests/e2e_tests/, mocked LLM).Summary by CodeRabbit