Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shard across multiple VMs #192

Closed
sourcefrog opened this issue Dec 15, 2023 · 0 comments · Fixed by #197
Closed

Shard across multiple VMs #192

sourcefrog opened this issue Dec 15, 2023 · 0 comments · Fixed by #197
Assignees
Labels
performance Making cargo mutants faster

Comments

@sourcefrog
Copy link
Owner

For CI builds and similar situations it would be nice to have an option --shard k/n that tests a subset of mutants. You could then, for example, launch 8 workers which each test 1/8th of the mutants in separate VMs, for example using GitHub Actions matrices. The tree is clean if they all succeed.

Compared to -j:

  • This is only useful if you have multiple machines to run on, so won't help on a laptop.
  • It would avoid the issues where high -j can cause RAM exhaustion or thrashing when all the builds or tests spike at the same time.
  • You'd get multiple independent outputs, but CI systems should handle the UI of showing which ones failed, and treating failure of any part as an overall failure.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance Making cargo mutants faster
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant