Fix flatware rspec spec/foo sometimes running the entire test suite
#111
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.
When there's a mix of timed & untimed files, the previous behaviour could produce a list of job groups with some empty elements in
JobBuilder#balancer_jobs.This could cause, eg,
flatware rspec ./spec/mailersto send an empty file list to one of the spawned workers, causing that worker to run every single spec under ./spec.I've also updated Cucumber::CLI & RSpec::CLI so that it doesn't spawn unnecessary workers if there's not enough jobs to fill them.
WDYT?