Add automatic lcov and cargo-fuzz installation to restore packages workflow #1592
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements automatic installation of
lcov
andcargo-fuzz
when runningxflowey restore
, addressing the feedback that these tools should be automatically installed rather than requiring manual setup.Changes Made
1. Created
flowey_lib_common/src/install_lcov.rs
lcov
installationinstall_git.rs
,install_nodejs.rs
, etc.)2. Enhanced Package Restoration Workflow
flowey_lib_hvlite/src/_jobs/local_restore_packages.rs
: Added bothlcov
andcargo-fuzz
installation as dependenciesflowey_lib_hvlite/src/_jobs/cfg_common.rs
: Integratedlcov
auto-installation configuration with existingauto_install
flag3. Improved User Experience
xtask/src/tasks/fuzz/html_coverage.rs
: Enhanced error message to suggest runningxflowey restore
whenlcov
is missingBefore
After
Verification
lcov
installation step appears in restore-packages workflow visualizationcargo-fuzz
installation step appears in restore-packages workflow visualizationxflowey restore
The implementation ensures that both
cargo xtask fuzz
coverage generation andxflowey restore
workflows now handle the complete fuzzing toolchain setup automatically, eliminating the need for manual package installation.Fixes #586.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.