You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All Client implementers have been helping us to reduce GitHub overhead, and download tests through the tarbal archives we provide. Cloning the spec-tests through git, even though it uses LFS, is very problematic for GitHub and CI providers, as it costs over a GB per clone, since it is not compressed during cloning. We merely use git for historical versioning, and it's not the intention to distribute it this way.
The tar files that are available however are much faster to download, and don't cause GitHub to rate-limit you when you clone more. Additionally, caching the spec-tests in your CI and local dev environment would be great.
May I suggest you add something like this to a makefile, to download the tests, and remove it as git submodule:
All Client implementers have been helping us to reduce GitHub overhead, and download tests through the tarbal archives we provide. Cloning the spec-tests through git, even though it uses LFS, is very problematic for GitHub and CI providers, as it costs over a GB per clone, since it is not compressed during cloning. We merely use git for historical versioning, and it's not the intention to distribute it this way.
The tar files that are available however are much faster to download, and don't cause GitHub to rate-limit you when you clone more. Additionally, caching the spec-tests in your CI and local dev environment would be great.
May I suggest you add something like this to a makefile, to download the tests, and remove it as git submodule:
Thank you!
The text was updated successfully, but these errors were encountered: