[CI,Windows] Build SPIRV-Tools separately #8276
Merged
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
ZeeWanderer
changed the title
|
Azure by default uses 2 cache contexts for PRs: master as read only, and the PR as read/write. It also does this caching very poorly. |
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.
Also, I think that if a single Intermediate dir is created it could be cached along with libs and bin folders to drastically speed up compilation, thou it would require not updating cache on Pull Requests at all or creating a separate cache per Pull Request and using either PR specific cache or falling back to the general cache on the first PR build if that is possible to do with azure at all.
EDIT:
I will try to do that in another PR so no longer WIP.