Split up vector_swizzle tests into smaller chunks to improve compilation times #901
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.
The vector swizzle tests are failing to compile on machines with 16 GB of RAM due to the huge size of some of the test .cpp files that are generated by the scripts. This PR makes the necessary changes to enforce splitting of these test files into smaller and more manageable files that can be compiled without requiring a large memory footprint. As of the time of this writing, I've chosen the number of batches aka chunks to be 32 so that each large file will be subdivided into 32 smaller files. I chose this number because with 16 chunks I was seeing flaky results where a compilation would succeed or fail depending on the state of the machine at the time of compilation. With 32 however, compilation was succeeding constantly. Nevertheless, this can easily be adjusted according to our needs.