Break up test suite further for CircleCI - #963
Merged
Merged
Conversation
kronosapiens
approved these changes
Jun 3, 2021
This file contains hidden or 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
2 participants
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.
While working on #962, ended up running in to this error. Slightly misleadingly, it's not strictly a lack of space, but a lack of inodes that it's running into, because ganache has a very file-generation-intensive way of running a blockchain.
Ordinarily, you fix this by just increasing the inode limit, but because these jobs run inside a docker container, which inherits the inode limit from the host, that's not an option for us as we don't have access to the host. Instead, we just have to manage the generation of these files.
This PR explicitly tells
ganachewhere to put those files, and in some cases on Circle deletes them between suites of tests (the non-coverage tests) and in other cases I've simply split the tests up in to separate jobs (the coverage tests).