Subject: | Suggestion: Distribute configurations over test runs |
On slow systems, testing several configurations takes a lot of time, and substantially more than what can be accomplished during the wee hours of the night.
I'd suggest a feature that each run of the smoker runs only one configuration. The next run of the smoker will run the next configuration, and so on. Although this is slightly less accurate than testing all configurations with the same snapshot of perl, it is much better than reducing the number of configurations due to time contraints.