Trying to spread unrelated topics into different threads, otherwise it's a mess:
Guilty as charged m'lud :-)
Steve Hay wrote: > I tried running "perl t/SMOKE" but I just get this: > > ===== > C:\Temp\modperl-2.0>perl t/SMOKE > *** Using random number seed: 1012582729 (autogenerated) > *** > ------------------------------------------------------------ > *** [001-00-00] trying all tests 10 times > !!! failed to start server > '.' is not recognized as an internal or external command, > operable program or batch file. > =====
Yup, it needs tweaking to run on win32.
Randy wrote: > Try changing this to "$^X /path/to/modperl-2.0/t/TEST". > However, when I tried running this it *seemed* to hang; > but I may have just been too impatient, or tired ...
What do you mean hanging? have you tried adding the -verbose flag? Did it start the server? Did it start running the first tests?
I tried "perl t/SMOKE -verbose=1" and it makes no difference.
It kicks off an Apach.exe which eats a bit of CPU for a short while and then everything goes quiet. Apache.exe stays sitting there, but doesn't seem to do anything else. I left it for nearly 2 hours and nothing happened. When I killed it, it dumped this into the report file:
#####
======= Special Tests Sequence Failure Finder Report =======
------------------------------------------------------------
First iteration used:
C:\perl\bin\perl.exe C:/Temp/modperl-2.0/t/TEST [snipped -- long list of tests]
------------------------------------------------------------
========================= Summary ========================== Completion : Not Completed (aborted by user) Status : Unknown Tests run : 0 Iterations (random) made : 0 ------------------------------------------------------------ --- Started at: Wed Sep 17 12:32:34 2003 --- --- Ended at: Wed Sep 17 14:15:22 2003 --- ------------------------------------------------------------ The smoke testing was run on the system with the following parameters:
[snipped -- Apache and Perl config info]
-- this report was generated by t/SMOKE #####
I tried just running a small subset of the tests, e.g. "perl t/SMOKE -verbose=1 t/compat", but that behaves the same.
What gives?
- Steve
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
