> > Automated smoke report for 5.9.0 patch 21356 on windows
> nt - 5.0 (x86)
> > (smoker) using version
> > Report by Test::Smoke v1.18.02 (perl 5.6.1) [2 minutes 32 seconds]
>
> I understand that this was yours...
Yep. it didnt run vsvars32 first so it couldnt find nmake...
> > configsmoke.pl dies if you dont specify a path to archive
> your smokes in.
>
> This has been resolved in the upcomming 1.18.06
Cool.
> > On win32/dotNet VS 6 etc, unless you copy the enviornment vars from
> > VCVARS32/VSVARS32 into the registry, and/or remember to run
> one of them
> > before you start smoking or configuring the correct paths
> will not be
> > searched and the various tools needed will not be found.
>
> Yes it has been on my todo for some time, but I currently
> have no access to a
> machine with MSVS... As soon as I find some time, I'll try
> and arrange that
Feel free to send me test code and ill give it a go.
Otherwise I could try to put together a patch for you. One trick is that
really it should ask to run v[cs]vars32 before it searches for compilers.
> Would the hangs be while "PERLIO=stdio :crlf"? (I have this
> problem with gcc
> on Win32.) If so you can try the "defaultenv" option [Run without
> $ENV{PERLIO}?].
Yes ill have a look.
> I can't realy do anything about hanging tests from
> Test::Smoke, but they
> occasionally occur on some systems.
Yeah. thats true. Im thinking there must be a way to simulate alarm on
Win32 however, ill see fi I can hack something together.
But I did find it strange the test ran fine from the cmdline.
Is it possible somehow the IO redirection involved with smoking trips
something up in perl?
Cheers,
Yves
