build(cmake): fail fast with clear diagnostic when .venv has no pip (5.1) - #14802
Conversation
A hand-rolled 'uv venv' (without --seed) creates a pip-less venv. QGC reuses it and configure later dies inside the mavlink CPM build with an opaque 'Python pip not found' error. Detect the missing pip up front and fail with instructions instead. Replaces mavlink#14767, which auto-bootstrapped pip via ensurepip; a read-only diagnostic avoids CMake silently mutating a user-managed venv.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## Stable_V5.1 #14802 +/- ##
==============================================
Coverage ? 32.68%
==============================================
Files ? 784
Lines ? 67602
Branches ? 31311
==============================================
Hits ? 22093
Misses ? 30632
Partials ? 14877
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
Build ResultsPlatform Status
All builds passed. Pre-commit
Pre-commit hooks: 0 passed, 0 failed, 0 skipped. Test Resultslinux-coverage-integration: 37 passed, 0 skipped Code CoverageCoverage: 69.4% No baseline available for comparison Artifact Sizes
Updated: 2026-08-09 17:06:42 UTC • Commit: bf63c70 • Triggered by: Android |
Cherry-pick of #14784 to Stable_V5.1.