At 1:30 AM -0400 9/22/01, Michael G Schwern wrote: >So like I said, either tests are habitually failing on vmsperl, or >nobody's compiled Perl on OS/390 in a long time (I wouldn't be >surprised if that were true). > >If there are tests that just fail all the time for you guys, post them >up and maybe we can fix them, or at least shut them up.
Dunno about OS/390 (try the perl-mvs list), but here's the list I got with perl@12088, Compaq C V6.4-005 on OpenVMS Alpha V7.3: [-.ext.list.util.t]tainted..............FAILED on test 3 [-.lib.extutils]manifest................FAILED on test 5 [-.lib.file.find.t]taint................FAILED on test 18 [-.lib.test.simple.t]todo...............FAILED on test 1 [.lib]vmsish............................FAILED on test 13 [.op]chdir..............................FAILED on test 1 [.run]kill_perl.........................FAILED on test 2 Failed 7/443 tests, 93.00% okay. I do frequent builds but don't usually post results unless I have a fix. Most of these will be difficult or impossible to debug without access to a VMS system. manifest.t and chdir.t assume case-preserving file systems. kill_perl.t runs fine by itself but not in the test suite. vmsish.t #13 is a known bug in the "vmsish 'hushed'" pragma. I haven't gotten too far with the others but can try to post detailed results if anyone is interested. -- ____________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "Literary critics usually know what they're talking about. Even if they're wrong." -- Perl creator Larry Wall
