windows ci: Run cargo clippy in the dev drive workspace to reuse the cache
#9411
+1
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
In the Windows Clippy job, the workspace is transferred to
UV_WORKSPACE. However,cargo clippycontinues to execute in thegithub.workspace, andSwatinem/rust-cacheonly caches theUV_WORKSPACE/target, resulting incargo clippyhaving no cache.This adjustment will take effect when any changes are made to
Cargo.tomlorCargo.lock, promptingSwatinem/rust-cacheto updat the cache.