Speed up WPT checkout #215
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
By shallow cloning and only cloning the master branch, the WPT setup can be sped up. See https://www.bram.us/2020/11/11/speed-up-build-times-with-this-little-git-trick/ details.
|
First results for Checkout WPT step:
|
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.
By shallow cloning and only cloning the master branch, the WPT setup can be sped up, thereby improving the overall speed of the build pipeline.
Without this change – and at the time of writing – 705377 files make up the entire WPT repo and its history. With it, only 89341 files need to be fetched.
See https://www.bram.us/2020/11/11/speed-up-build-times-with-this-little-git-trick/ for details about this trick.