Looks like it was just a false alarm... I re-ran nmake test and it came back successful... Sorry for the confusion...
John Kizlyk Sr. Security Systems Engineer -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 17, 2007 9:02 AM To: Kizlyk, John Cc: [email protected] Subject: Re: FAIL IPC-Cmd-0.40 MSWin32-x86-multi-thread 5.00 Greetings, On 17 Oct 2007, at 15:53, John Kizlyk wrote: > Output from 'C:\vs8\vc\bin\nmake.EXE test': > > > Microsoft (R) Program Maintenance Utility Version 8.00.50727.762 > Copyright (C) Microsoft Corporation. All rights reserved. > > C:\Perl\bin\perl.exe "-MExtUtils::Command::MM" "-e" "test_harness > (0, 'blib\lib', 'blib\arch')" t/*.t > t/01_IPC-Cmd........Unknown error on port 2079 > Unknown error on port 2080 > Unknown error on port 2081 > Unknown error on port 2082 > Unknown error on port 2083 > Unknown error on port 2084 > Unknown error on port 2085 > Unknown error on port 2086 > Unknown error on port 2087 > Unknown error on port 2088 > Unknown error on port 2089 at C:/Perl/site/lib/IPC/Run.pm line 2225 > # Looks like your test died just after 209. What a most interesting error report. I've never seen anything like it. As far as I know, IPC::Cmd does not use any ports in it's test suites, and only uses the $^X program (path to your perl) to do command line tests. Could you shed some light on what's going on? -- Jos Boumans How do I prove I'm not crazy to people who are?
