test(bootstrapper): fix caplog assertion that depends on global pytes…

[shifa-khan]

Use caplog.at_level(logging.INFO) for the bootstrapper logger so the test doesn't rely on --log-level DEBUG being passed by the runner.

Closes: #1092

• PR follows CONTRIBUTING.md guidelines

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR fixes a test flakiness issue in test_cache_lookup_resolver_exception_logs_info by making log-level assertions self-contained. The test previously relied on a global pytest --log-level DEBUG flag to capture INFO-level logs. The change adds import logging and wraps the test's resolver call with caplog.at_level(logging.INFO, logger="fromager.bootstrapper"), ensuring the test explicitly requests the log level it needs rather than depending on runner-wide configuration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: fixing a caplog assertion that depends on global pytest log-level configuration.
Linked Issues check	✅ Passed	The PR fully addresses issue #1092 by implementing the proposed solution: using caplog.at_level(logging.INFO, logger="fromager.bootstrapper") to make the test self-contained.
Out of Scope Changes check	✅ Passed	All changes are directly related to fixing the test dependency on global pytest log-level; no extraneous modifications are present.
Description check	✅ Passed	The pull request description clearly relates to the changeset, explaining the specific fix of using caplog.at_level(logging.INFO) to make the test self-contained.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[rd4398]

LGTM