A few things here. I've been looking at the different reports coming in and so I wanted to change my config to test some of the more exotic variants. It seems pointless to smoke bincompat5005 for 5.9.0. So COW seemed like a good thing to try out.
I tried adding
== /-DPERL_COPY_ON_WRITE/
-DPERL_COPY_ON_WRITE
to the end of my config but that spits out an error:
make distclean ...
Copy Policy.sh ...Policy target '-DPERL_COPY_ON_WRITE' failed to match at /usr/local/perlsmoke/Test/Smoke/Smoker.pm line 270
Looking at other reports, it looks like -Accflags='-DPERL_COPY_ON_WRITE' is what's required. So should my section look like
== /-Accflags='-DPERL_COPY_ON_WRITE'/
-Accflags='-DPERL_COPY_ON_WRITE'
It would be helpful if the config that was used for the smoke (sans comments) was tacked onto the end of the report. Also, how can I add a -j switch to make, in order to run tests in parallel? My configure-fu is not strong enough to figure it out.
I have patched smokerstatus.pl to print out the mean smoke duration. I don't have a diff, but it just involves adding the following line:
print "$rpt->{count} out of $ccnt configurations finished in $rpt->{time}.\n",
"Mean smoke duration: @{[time_in_hhmm(int $rpt->{avg})]}.\n";
printf "$rpt->{fail} configuration%s showed failures%s.\n",
($rpt->{fail} == 1 ? "" : "s"), $rpt->{stat} ? " ($rpt->{stat})" : "";
Once you have an idea of the mean smoke duration, it is possible to run smokerstatus.pl in a loop, to keep an eye on things:
% cat smokersloop
#! /bin/sh
SLEEPTIME=900
if [ "$1x" = "x" ]
then
echo "No config file given on command line"
exit
fi
if [ "$2x" = "x" ]
then
echo "No sleep time given, using default $SLEEPTIME"
else
SLEEPTIME=$2
fi
while true
do
/usr/local/perlsmoke/smokestatus.pl -c $1
sleep $SLEEPTIME
doneAnd then you can see if a smoke has become wedged. And once again... after a successful smoke of 5.9.x, once again I have a test that is stuck in limbo:
./perl -I. -MTestInit ../ext/IO/t/io_multihomed.t
... has been stuck on this for six hours. All I know is that this is the first smoke configuration in which -Duseithreads has been issued. And yet my previous smoke of 21451 went through without a hitch.
Anyway, my apologies for not splitting this babble up into multiple posts. Thanks for listening.
David
