It's a little more complicated - I have to sync the repository up first, and only run if something has changed.
That's why there is 'smartsmoke', F<smokeperl.pl> will check if the patchlevel changed after its synctree-step. No change, no smoke...
Yes, but my UberSmoke script needs not to keep calling smokeperl.pl in a tight loop when there is actually nothing to do, hence it need to know as well. No problem, I already have this sorted out.
Another RFE is for a 'status' command that shows you how many tests of a run have completed.
Individual tests per configuration/$ENV{PERLIO} cannot be determined. But I can interpret the F<mktest.out> file and match it against the buildconfig file and report what is already done and what is still to be expected.
But that will have to wait until 1.19 for which I've planned to modularise F<mkovz.pl> in such a way that this sort of thing is easy...
Yes, I'm not really bothered about individual test status, more like
'5 of 27 configurations tested, 2 configurations failed tests'
or similar. A 'started ad date' and 'estimated completion by' would be a bonus ;-)
-- Alan Burlison --
