Randy Kobes wrote:
On Wed, 8 Oct 2003, Stas Bekman wrote:


Steve Hay wrote:

[ .. ]


Do you have the same issue if you run them as:

perl t/TEST testname

instead of using 'nmake'? If that's the case, it's not an issue with SMOKE.


Running the tests that fail under t/SMOKE as
   perl t/TEST testname
reports them passing.

Thanks, Randy. And if you run:


perl t/TEST -start
perl t/TEST -run testname
perl t/TEST -stop

if this still works, what if you run TestSmoke's test_run alone by ripping it off and just hardcoding things?

I've attached a patch (for Steve's benefit, as it's Win32
specific) which, first of all, uses Win32::Process (to
rule out problems coming from IPC::Run3), and which defines
two functions:
   run_command - uses system() to run a command, and
                 returns a flag indicating success;
   run_command_dup - uses Win32::Process to run a command,
                     capturing the STDOUT and STDERR and
                     then returning the text.

- if one uses run_command_dup to start/stop the server and
run the tests, then the error with failing to dup STDOUT
results, for those tests that use perl-script.
- if one uses run_command_dup to start/stop the server, but
uses run_command to run the tests, then the same error
results.
- if one uses run_command to start/stop the server and run
the tests, then all tests pass.

What about the 4th option:


- if one uses run_command to start/stop the server and
uses run_command_dup to run the tests, ...

also isn't the third option exactly what we have now with IPC::Run? (i.e. using system everywhere?)

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to