Skip Menu |

This queue is for tickets about the Test-Smoke CPAN distribution.

Report information
The Basics
Id: 90154
Status: rejected
Priority: 0/
Queue: Test-Smoke

People
Owner: Nobody in particular
Requestors: jv [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



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.
On Fri Nov 08 10:49:57 2013, JV wrote: Hi Johan, [ 3.5 years is quite a wait, sorry!] Show quoted text
> 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.
This is explicitly what Test::Smoke was not designed to do :-) One could split the build-config file into separate configs and loop over them. The chkbcfg.pl script could help you to do that. For the moment, I'm going to reject your request. Thanks for interest in Test::Smoke! On behalf of the Test::Smoke team, -- Abe.