fix(resolver): log wheel-only candidate skips at INFO - #1354
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 17 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configurationConfiguration used: Repository: python-wheel-build/fromager/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: python-wheel-build/fromager/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthrough
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~5 minutes Merge Risk: ⚪ Minimal · up to The change lowers routine wheel-only skip messages to INFO while preserving the skip behavior. No actionable merge risk is indicated. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
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 |
Keep routine candidate skips in CI logs without sending WARNING telemetry events. Co-Authored-By: Codex <codex@openai.com> Signed-off-by: Ryan Petrello <rpetrell@redhat.com>
bc79044 to
e263ce9
Compare
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
Lower the verbosity of routine candidate skips without generating noisy WARNING telemetry events.
In complex runs of fromager, especially ones in multi-version mode, this
logger.warn()call results in an extremely verbose amount of output (roughly 80% ofWARNlevel output).Also, this message reports candidate filtering, not a failed resolution, so
WARNis excessive.