- [ ] Have you followed the guidelines for contributing? - [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? - [ ] Have you successfully run `tox`? ----- ## Description Fixes the integration test failures reported in [workflow run 19569214460](https://github.com/canonical/craft-providers/actions/runs/19569214460/job/56038422239) where tests were failing because the required LXD remotes were not configured in the GitHub Actions CI environment. The test `test_configure_and_launch_remote` and related tests were failing with: ``` Error: The remote "craft-com.ubuntu.cloud-buildd" doesn't exist Error: The remote "craft-com.ubuntu.cloud-buildd-daily" doesn't exist ``` ## Changes Made Added a session-scoped fixture `configure_lxd_remotes` in `tests/integration/lxd/conftest.py` that: - Automatically runs before all LXD integration tests (using `autouse=True` and `scope="session"`) - Configures the required buildd remotes (`craft-com.ubuntu.cloud-buildd` and `craft-com.ubuntu.cloud-buildd-daily`) - Uses the existing `RemoteImage.add_remote()` method for proper error handling and race condition management This follows the same pattern used in `LXDProvider.launched_environment()` where `image.add_remote()` is called before launching instances. ## Testing - ✅ Python syntax check passed - ✅ Ruff linting passed - ✅ Code review completed with no blocking issues - ✅ CodeQL security scan passed with no vulnerabilities The fix ensures that integration tests will work in any environment where LXD is installed but remotes haven't been pre-configured, which is the case in the GitHub Actions CI environment. <!-- START COPILOT ORIGINAL PROMPT --> <details> <summary>Original prompt</summary> > Reference: https://github.com/canonical/craft-providers/actions/runs/19569214460/job/56038422239 > > Fix these test failures </details> <!-- START COPILOT CODING AGENT TIPS --> --- 💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey).