On Tue 04 Mar 2003 06:01, Christopher Faylor <[EMAIL PROTECTED]> wrote: > On Wed, Feb 26, 2003 at 03:20:02PM +0100, H.Merijn Brand wrote: > >On Tue 25 Feb 2003 14:15, "H.Merijn Brand" <[EMAIL PROTECTED]> wrote: > >> ../ext/IO/lib/IO/t/io_udp..............ok > >> ../ext/IO/lib/IO/t/io_unix.............ok 1/5 > >> > >> 20030220 still OK > > > >20030225 also hangs > > > >(Note that I'm still not on the list) > > Is it better now? > > cgf
Yep. CYGWIN_NT-5.0 PC09 1.3.21s(0.77/3/2) 20030302 23:00:55 i686 unknown unknown Cygwin Completed the smoke. I was discussing a longstanding Cygwin issue yesterday with some other smokers and we all agreed that there is still a glitch in cygwin that /we/ think cygwin is to blame for. Running the complete test from the prompt completes without error, but when started from a script in the background, there are still messages that get a <CR> added and unexpectedly yield <CR><NL> instead of plain <NL>, causing these tests to fail: Expected Foo<NL>, got Foo<CR><NL> $CYGWIN is "tty ntsec binary" If you can fix this, you can add Cygwin to one of the systems where smokes on bleadperl yield a full-O (all OK) report. Enjoy, have FUN! H.Merijn -- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.8.0 & 633 on HP-UX 10.20 & 11.00, AIX 4.2, AIX 4.3, WinNT 4, Win2K pro & WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED] http://archives.develooper.com/[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
