Skip Menu |
Report information
Id: 21442
Status: resolved
Priority: 0/
Queue: perl5

Owner: Nobody
Requestors: elmisery_fathy [at] hotmail.com
Cc: bulk88 <bulk88 [at] hotmail.com>
AdminCc:

Operating System: Win32
PatchStatus: (no value)
Severity: low
Type: unknown
Perl Version: (no value)
Fixed In: (no value)



From: "fathy elmisery" <elmisery_fathy [...] hotmail.com>
To: perlbug [...] perl.org
BCC:
Subject: some tests fail
Date: Mon, 03 Mar 2003 20:53:50 +0000
Dear perl support
i am design engineer from egypt i downloaded the perl vesion 5.8.0 and i installed it but i got some tests failed and the output of the message in the attachment file perlfail.doc. i am using windows 2000 nt technology and the compiler is MSV(microsoft visual studio ) version 6.0.
can you help me for solving this problems.
                  thank you for your kind help.


 

elmisery


MSN 8 with e-mail virus protection service: 2 months FREE*
Download myconfig.SH
text/plain 2.5k

Message body is not shown because sender requested not to inline it.

Download perlfail.doc
application/msword 37.5k

Message body not shown because it is not plain text.

From: "fathy elmisery" <elmisery_fathy [...] hotmail.com>
To: perlbug-followup [...] perl.org
BCC:
Subject: [perl #21442]
Date: Wed, 05 Mar 2003 11:01:34 +0000
RT-Send-Cc:
Download (untitled) / with headers
text/plain 2.9k
dear perl support that is the reply to your message about my problem with the some tests fails. can you help me about this problem. thanks for your help. <br><br><br><html><DIV>elmisery</DIV></html> Show quoted text
>case $PERL_CONFIG_SH in >'') > if test -f config.sh; then TOP=.; > elif test -f ../config.sh; then TOP=..; > elif test -f ../../config.sh; then TOP=../..; > elif test -f ../../../config.sh; then TOP=../../..; > elif test -f ../../../../config.sh; then TOP=../../../..; > else > echo "Can't find the perl config.sh file produced by Configure"; > exit 1 > fi > . $TOP/config.sh > ;; >esac >: This forces SH files to create target in same directory as SH file. >: This is so that make depend always knows where to find SH derivatives. >case "$0" in >*/*) cd `expr X$0 : 'X\(.*\)/'` ;; >esac >echo "Extracting myconfig (with variable substitutions)" >$spitshell >myconfig <<!GROK!THIS! >$startsh > ># This script is designed to provide a handy summary of the configuration ># information being used to build perl. This is especially useful if you ># are requesting help from comp.lang.perl.misc on usenet or via mail. > ># Note that the text lines /^Summary of/ .. /^\s*$/ are copied into >Config.pm. >cat <<'!NO!SUBS!' >Summary of my $package (revision $baserev $version_patchlevel_string) >configuration: > Platform: > osname=$osname, osvers=$osvers, archname=$archname > uname='$myuname' > config_args='$config_args' > hint=$hint, useposix=$useposix, d_sigaction=$d_sigaction > usethreads=$usethreads use5005threads=$use5005threads >useithreads=$useithreads usemultiplicity=$usemultiplicity > useperlio=$useperlio d_sfio=$d_sfio uselargefiles=$uselargefiles >usesocks=$usesocks > use64bitint=$use64bitint use64bitall=$use64bitall >uselongdouble=$uselongdouble > usemymalloc=$usemymalloc, bincompat5005=undef > Compiler: > cc='$cc', ccflags ='$ccflags', > optimize='$optimize', > cppflags='$cppflags' > ccversion='$ccversion', gccversion='$gccversion', >gccosandvers='$gccosandvers' > intsize=$intsize, longsize=$longsize, ptrsize=$ptrsize, >doublesize=$doublesize, byteorder=$byteorder > d_longlong=$d_longlong, longlongsize=$longlongsize, >d_longdbl=$d_longdbl, longdblsize=$longdblsize > ivtype='$ivtype', ivsize=$ivsize, nvtype='$nvtype', nvsize=$nvsize, >Off_t='$lseektype', lseeksize=$lseeksize > alignbytes=$alignbytes, prototype=$prototype > Linker and Libraries: > ld='$ld', ldflags ='$ldflags' > libpth=$libpth > libs=$libs > perllibs=$perllibs > libc=$libc, so=$so, useshrplib=$useshrplib, libperl=$libperl > gnulibc_version='$gnulibc_version' > Dynamic Linking: > dlsrc=$dlsrc, dlext=$dlext, d_dlsymun=$d_dlsymun, >ccdlflags='$ccdlflags' > cccdlflags='$cccdlflags', lddlflags='$lddlflags' > >!NO!SUBS! >!GROK!THIS! >chmod 755 myconfig >$eunicefix myconfig
Show quoted text
_________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 315b
This ticket has been languishing in our bug queue since 2003. List: Is there anyone of Win32 who could take a look at the Word document the OP provided and offer some suggestions? fathy elmisery: Have you tried any Perl distributions on Windows such as Win32 or Strawberry Perl? Thank you very much. Jim Keenan
RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 362b
On Sat Apr 21 15:14:29 2012, jkeenan wrote: Show quoted text
> This ticket has been languishing in our bug queue since 2003. > > List: Is there anyone of Win32 who could take a look at the Word > document the OP provided and offer some suggestions?
The word document only contains a graphic. Here it is, attached as a PNG. It’s not very helpful. -- Father Chrysostomos
RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 507b
Show quoted text
> The word document only contains a graphic. Here it is, attached as a > PNG. It’s not very helpful. >
That is a problem. The OP doesn't say what tests failed. Since these are I/O failures in general looking at the 2 test files, and only happened on OP's machine, I'm going to guess a firewall or virus scanner or security permissions caused them. If someone can reproduce them I'll look into it. I dont think anyone will be able to, I couldn't with those 2 test files with my VC Perl 5.15 and AP 5.10.
RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 786b
On Sat Apr 21 19:02:57 2012, bulk88 wrote: Show quoted text
> > The word document only contains a graphic. Here it is, attached as a > > PNG. It’s not very helpful. > >
> That is a problem. The OP doesn't say what tests failed. Since these are > I/O failures in general looking at the 2 test files, and only happened > on OP's machine, I'm going to guess a firewall or virus scanner or > security permissions caused them. If someone can reproduce them I'll > look into it. I dont think anyone will be able to, I couldn't with those > 2 test files with my VC Perl 5.15 and AP 5.10.
Thanks for your response. I propose that we keep the ticket open for 30 days. If we get the errors reproduced, you can take up the investigation. Otherwise, we'll close the ticket. Thank you very much. Jim Keenan
RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 5.7k
My mistake, I see the error numbers that failed. for fs.t 2-5 involve NTFS POSIX hard links, whether link works is determined by if (defined &Win32::IsWinNT && Win32::IsWinNT()) { if (Win32::FsType() eq 'NTFS') { $has_link = 1; $accurate_timestamps = 1; } } FsType gets the FS type of the current directory, as thought of by the Windows API. This might not be the current directory thought of by the Perl Language (ithreads, etc). 7-9 are chmod, thats also dependent on NTFS and links check above test 11, egh, not sure if this is the same as OP's 5.8 tests, i cant comment 5 and 7 in stat.t again are link tests I'm going to blindly guess the OP has multiple partitions or perl isn't install on C: or C: isn't the windows OS dir, and somehow perl thought it was running on NTFS when it was actually a fat partition. below done with perl 5.10.1 tests on 5.10.0 (best I can do) C:\Perl\t>perl ./io/fs.t 1..51 ok 1 # skip bogus umask ok 2 - link a b ok 3 - link b c ok 4 - link count of triply-linked file ok 5 - mode of triply-linked file ok 6 - chmod succeeding ok 7 - chmod going through ok 8 - chmod two files ok 9 - chmod going through to c ok 10 - chmod going through to x ok 11 - unlink two files ok 12 - ino of removed file b should be undef ok 13 - ino of removed file x should be undef ok 14 # skip no fchmod ok 15 # skip no fchmod ok 16 # skip no fchmod ok 17 # skip no fchmod ok 18 # skip no fchmod ok 19 # skip no fchown ok 20 - fchmod is unimplemented ok 21 - fchown is unimplemented ok 22 - rename a b ok 23 - ino of renamed file a should be undef ok 24 - utime ok 25 # skip bogus inode num # atime - 500000000 mtime - 500000001 delta - 1 ok 26 - atime ok 27 - mtime # utime undef, undef --> 1335072593, 1335072593 ok 28 - atime ok 29 - mtime ok 30 # skip no futimes ok 31 # skip no futimes ok 32 # skip no futimes ok 33 # skip no futimes ok 34 - futimes is unimplemented ok 35 - unlink b ok 36 - ino of unlinked file b should be undef ok 37 # skip No symbolic links found to test with ok 38 # skip No symbolic links found to test with ok 39 - truncation to five bytes ok 40 - truncation to zero bytes ok 41 - fh resize to 200 ok 42 - fh resize to 200 working (filename check) ok 43 - fh resize to zero ok 44 - fh resize to zero working (filename check) ok 45 - fh resize by IO slot ok 46 - fh resize by IO slot working ok 47 - rename working ok 48 - rename on directories ok 49 - rename on directories working ok 50 - extend sp in pp_chmod ok 51 - extend sp in pp_chown C:\Perl\t> C:\Perl\t>perl ./op/stat.t 1..107 ok 1 - nlink on regular file ok 2 # skip mtime and ctime not reliable ok 3 # skip mtime and ctime not reliable ok 4 - link() implemented ok 5 - linked tmp testfile ok 6 - chmoded tmp testfile ok 7 - Link count on hard linked file ok 8 # skip No ctime concept on this OS ok 9 # skip No ctime concept on this OS ok 10 - -z on empty filehandle ok 11 - and -s ok 12 - -z on empty file ok 13 - and -s ok 14 - -z on empty filehandle ok 15 - and -s ok 16 - -z on non-empty file ok 17 - and -s ok 18 - chmod 0000 ok 19 # skip Can't test -r or -w meaningfully if you're superuser ok 20 # skip Can't test -r or -w meaningfully if you're superuser ok 21 - -x ok 22 - chmod 0700 ok 23 - -r ok 24 - -w ok 25 # skip -x simply determines if a file ends in an executable suffix ok 26 - -f ok 27 - !-d ok 28 - -d cwd ok 29 - !-f cwd ok 30 # skip symlink not implemented ok 31 # skip symlink not implemented ok 32 # skip symlink not implemented ok 33 - -o ok 34 - -e ok 35 - -e on unlinked file ok 36 # skip No character, socket or block special files ok 37 # skip No character, socket or block special files ok 38 # skip No character, socket or block special files ok 39 # skip No character, socket or block special files ok 40 # skip No character, socket or block special files ok 41 # skip No character, socket or block special files ok 42 # skip Can't find a setuid file to test with ok 43 # skip Can't find a setuid file to test with ok 44 # skip Can't find a setuid file to test with ok 45 # skip Test uses unixisms ok 46 # skip Test uses unixisms ok 47 - !-t on closed TTY filehandle ok 48 - -t on STDIN ok 49 # skip No null device to test with ok 50 - -T ok 51 - !-B ok 52 - -B ok 53 - !-T ok 54 - -T on filehandle causes no errors ok 55 - -T ok 56 - !-B ok 57 - after readline ok 58 - still -T ok 59 - still -B ok 60 - reopened and after readline ok 61 - still -T ok 62 - still !-B ok 63 - after seek ok 64 - still -T ok 65 - still !-B ok 66 - at EOF ok 67 - still -T ok 68 - now -B ok 69 # skip No null device to test with ok 70 # skip No null device to test with ok 71 - bare -f uses $_ ok 72 - -f() " ok 73 - stat returns full 13 elements ok 74 - lstat _ croaks after stat ok 75 - -l _ croaks after stat ok 76 - lstat _ ok after lstat ok 77 - -l _ ok after lstat ok 78 # skip No lstat ok 79 # skip No lstat # Zzz... ok 80 - can create tmp file # time=1335072680, stat=(2 0 33206 1 0 0 2 0 1335072683 1335072683 1335072683 ) # -MAC=(-3.47222222222222e-005 -3.47222222222222e-005 -3.47222222222222e-005) ok 81 - negative -M works ok 82 - negative -A works ok 83 - negative -C works ok 84 - unlink tmp file ok 85 - can create temp file ok 86 - -T _ doesn't break the statbuffer ok 87 # skip No dirfd() ok 88 # skip No dirfd() ok 89 # skip No dirfd() ok 90 # skip No dirfd() ok 91 # skip No dirfd() ok 92 # skip No dirfd() ok 93 # skip No dirfd() ok 94 # skip No dirfd() ok 95 # skip No dirfd() ok 96 - can create temp file ok 97 - stat(*F{IO}) works ok 98 - single file tests work with *F{IO} ok 99 # skip No dirfd() ok 100 # skip No dirfd() ok 101 # skip No dirfd() ok 102 # skip No dirfd() ok 103 # skip No dirfd() ok 104 # skip No dirfd() ok 105 # skip No dirfd() ok 106 # skip No dirfd() ok 107 # skip No dirfd() C:\Perl\t>
RT-Send-CC: perl5-porters [...] perl.org
Closing, since it doesn't appear that we have been able to reproduce this. -doy
Subject: core tests fail when built on FAT drive with Win32 OS on NTFS drive
RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 11.3k
On Tue Jul 03 00:06:38 2012, doy wrote: Show quoted text
> Closing, since it doesn't appear that we have been able to reproduce this. > > -doy
Someone with ticket privilege needs to change this ticket to open, see last paragraph of this post for details. I previously was not able to reproduce this when I last looked at this ticket, but by chance, I got a nearly identical test fail list on 5.19 blead to the OP from 2003. This is how to reproduce it. The Windows OS drive is NTFS, but you build Perl on FAT32 or FAT16. 1 Mechanical HD with Win OS on NTFS and 2nd FAT32 partition or usb stick with FAT16 made these failures for me. FAT32 build drive, OS on NTFS. OS is NOT on C: drive here. --------------------------------------------------------- C:\perl519\src\t> ..\perl.exe -I..\lib op/stat.t 1..113 ok 1 - nlink on regular file ok 2 # skip mtime and ctime not reliable ok 3 # skip mtime and ctime not reliable ok 4 - link() implemented not ok 5 - linked tmp testfile # Failed test 5 - linked tmp testfile at op/stat.t line 103 ok 6 - chmoded tmp testfile not ok 7 - Link count on hard linked file # Failed test 7 - Link count on hard linked file at op/stat.t line 113 # got "1" # expected "2" ok 8 # skip No ctime concept on this OS ok 9 # skip No ctime concept on this OS ok 10 - -z on empty filehandle ok 11 - and -s ok 12 - -z on empty file ok 13 - and -s ok 14 - -z on empty filehandle ok 15 - and -s ok 16 - -z on non-empty file ok 17 - and -s ok 18 - chmod 0000 ok 19 # skip Can't test -r or -w meaningfully if you're superuser ok 20 # skip Can't test -r or -w meaningfully if you're superuser ok 21 - -x ok 22 - chmod 0700 ok 23 - -r ok 24 - -w ok 25 # skip -x simply determines if a file ends in an executable suffix ok 26 - -f ok 27 - !-d ok 28 - -d cwd ok 29 - !-f cwd ok 30 # skip symlink not implemented ok 31 # skip symlink not implemented ok 32 # skip symlink not implemented ok 33 - -o ok 34 - -e ok 35 - -e on unlinked file ok 36 # skip No character, socket or block special files ok 37 # skip No character, socket or block special files ok 38 # skip No character, socket or block special files ok 39 # skip No character, socket or block special files ok 40 # skip No character, socket or block special files ok 41 # skip No character, socket or block special files ok 42 # skip Can't find a setuid file to test with ok 43 # skip Can't find a setuid file to test with ok 44 # skip Can't find a setuid file to test with ok 45 # skip Test uses unixisms ok 46 # skip Test uses unixisms ok 47 - !-t on closed TTY filehandle ok 48 - -t on STDIN ok 49 # skip No null device to test with ok 50 - -T ok 51 - !-B ok 52 - -B ok 53 - !-T ok 54 - -T on filehandle causes no errors ok 55 - -T ok 56 - !-B ok 57 - after readline ok 58 - still -T ok 59 - still -B ok 60 - reopened and after readline ok 61 - still -T ok 62 - still !-B ok 63 - after seek ok 64 - still -T ok 65 - still !-B ok 66 - at EOF ok 67 - still -T ok 68 - now -B ok 69 # skip No null device to test with ok 70 # skip No null device to test with ok 71 - bare -f uses $_ ok 72 - -f() " ok 73 - stat returns full 13 elements ok 74 - lstat _ croaks after stat ok 75 - lstat *_ croaks after stat ok 76 - lstat \*_ croaks after stat ok 77 - -l _ croaks after stat ok 78 - lstat _ ok after lstat ok 79 - -l _ ok after lstat ok 80 - stat $ioref resets stat type ok 81 - lstat $ioref reverts to regular fstat ok 82 # skip No lstat ok 83 # skip No lstat # Zzz... ok 84 - can create tmp file # time=1393701938, stat=(2 0 33206 1 0 0 2 0 1393650000 1393701944 1393701943 ) # -MAC=(-6.94444444444444e-005 0.601134259259259 -5.78703703703704e-005) ok 85 - negative -M works not ok 86 - negative -A works # Failed test 86 - negative -A works at op/stat.t line 504 ok 87 - negative -C works ok 88 - unlink tmp file ok 89 - can create temp file ok 90 - -T _ doesn't break the statbuffer ok 91 # skip No lstat ok 92 # skip No dirfd() ok 93 # skip No dirfd() ok 94 # skip No dirfd() ok 95 # skip No dirfd() ok 96 # skip No dirfd() ok 97 # skip No dirfd() ok 98 # skip No dirfd() ok 99 # skip No dirfd() ok 100 # skip No dirfd() ok 101 - can create temp file ok 102 - stat(*F{IO}) works ok 103 - single file tests work with *F{IO} ok 104 # skip No dirfd() ok 105 # skip No dirfd() ok 106 # skip No dirfd() ok 107 # skip No dirfd() ok 108 # skip No dirfd() ok 109 # skip No dirfd() ok 110 # skip No dirfd() ok 111 # skip No dirfd() ok 112 # skip No dirfd() ok 113 - no unopened warning from stat _ C:\perl519\src\t> ..\perl.exe -I..\lib io/fs.t 1..55 ok 1 # skip bogus umask not ok 2 - link a b # Failed test 2 - link a b at io/fs.t line 101 not ok 3 - link b c # Failed test 3 - link b c at io/fs.t line 102 not ok 4 - link count of triply-linked file # Failed test 4 - link count of triply-linked file at io/fs.t line 112 # got undef # expected "3" not ok 5 - mode of triply-linked file # Failed test 5 - mode of triply-linked file at io/fs.t line 122 # got "00" # expected "0666" ok 6 - chmod succeeding not ok 7 - chmod going through # Failed test 7 - chmod going through at io/fs.t line 142 # got "0" # expected "292" not ok 8 - chmod two files # Failed test 8 - chmod two files at io/fs.t line 149 # got "1" # expected "2" not ok 9 - chmod going through to c # Failed test 9 - chmod going through to c at io/fs.t line 157 # got "0" # expected "438" ok 10 - chmod going through to x not ok 11 - unlink two files # Failed test 11 - unlink two files at io/fs.t line 169 # got "1" # expected "2" ok 12 - ino of removed file b should be undef ok 13 - ino of removed file x should be undef ok 14 # skip no fchmod ok 15 # skip no fchmod ok 16 # skip no fchmod ok 17 # skip no fchmod ok 18 # skip no fchmod ok 19 # skip no fchown ok 20 - fchmod is unimplemented ok 21 - fchown is unimplemented ok 22 - rename a b ok 23 - ino of renamed file a should be undef ok 24 - utime ok 25 # skip bogus inode num ok 26 # skip filesystem atime/mtime granularity too low ok 27 # skip filesystem atime/mtime granularity too low # utime undef, undef --> 1393650000, 1393714698 ok 28 - atime ok 29 - mtime ok 30 # skip no futimes ok 31 # skip no futimes ok 32 # skip no futimes ok 33 # skip no futimes ok 34 - futimes is unimplemented ok 35 - unlink b ok 36 - ino of unlinked file b should be undef ok 37 # skip No symbolic links found to test with ok 38 # skip No symbolic links found to test with ok 39 - truncation to five bytes ok 40 - truncation to zero bytes ok 41 - fh resize to 200 ok 42 - fh resize to 200 working (filename check) ok 43 - fh resize to zero ok 44 - fh resize to zero working (filename check) ok 45 - fh resize by IO slot ok 46 - fh resize by IO slot working ok 47 - truncate(word) does not fall back to file name ok 48 - rename working ok 49 - rename on directories ok 50 - rename on directories working ok 51 - extend sp in pp_chmod ok 52 - extend sp in pp_chown ok 53 - can't unlink directory without -U and privileges ok 54 - unlink directory without -U sets errno ok 55 - unlink non-existent directory without -U sets ENOENT ------------------------------------------------------ building perl on usb stick (F: drive) ------------------------------------------------------ usb stick ------------------- ../lib/vmsish.t ................................................... ok ../lib/warnings.t ................................................. ok x2p/find2perl.t ................................................... skipped: Nee d something vaguely POSIX x2p/s2p.t ......................................................... ok Test Summary Report ------------------- io/fs.t (Wstat: 0 Tests: 55 Failed: 8) Failed tests: 2-5, 7-9, 11 op/stat.t (Wstat: 0 Tests: 113 Failed: 3) Failed tests: 5, 7, 86 Files=2407, Tests=691806, 17365 wallclock secs (142.05 usr + 6.55 sys = 148.59 CPU) Result: FAIL NMAKE : fatal error U1077: '..\perl.exe' : return code '0xb' Stop. F:\perl\win32> ------------------------------------------------------- I didn't step it or write additional code, so this analysis may be shoddy. The problem with io/fs.t is this check ---------------------------------------------------- if (defined &Win32::IsWinNT && Win32::IsWinNT()) { if (Win32::FsType() eq 'NTFS') { $has_link = 1; $accurate_timestamps = 1; } } ---------------------------------------------------- Win32::FsType's docs are ---------------------------------------------------- Win32::FsType() [CORE] Returns the name of the filesystem of the currently active drive (like 'FAT' or 'NTFS'). In list context it returns three values: (FSTYPE, FLAGS, MAXCOMPLEN). FSTYPE is the filesystem type as before. FLAGS is a combination of values of the following table: ---------------------------------------------------- "currently active drive" is the problem. There is probably something to do with that code not working right. ---------------------------------------------------- F:\perl\win32>cd ..\t F:\perl\t>perl -I..\lib harness io/fs.t io/fs.t .. # Failed test 2 - link a b at io/fs.t line 101 # Failed test 3 - link b c at io/fs.t line 102 # Failed test 4 - link count of triply-linked file at io/fs.t line 112 # got undef # expected "3" # Failed test 5 - mode of triply-linked file at io/fs.t line 122 # got "00" # expected "0666" # Failed test 7 - chmod going through at io/fs.t line 142 # got "0" # expected "292" # Failed test 8 - chmod two files at io/fs.t line 149 # got "1" # expected "2" # Failed test 9 - chmod going through to c at io/fs.t line 157 # got "0" # expected "438" # Failed test 11 - unlink two files at io/fs.t line 169 # got "1" # expected "2" io/fs.t .. Failed 8/55 subtests (less 16 skipped subtests: 31 okay) Test Summary Report ------------------- io/fs.t (Wstat: 0 Tests: 55 Failed: 8) Failed tests: 2-5, 7-9, 11 Files=1, Tests=55, 3 wallclock secs ( 0.08 usr + 0.02 sys = 0.09 CPU) Result: FAIL F:\perl\t> F:\perl\t>perl -I..\lib harness op/stat.t op/stat.t .. # Failed test 5 - linked tmp testfile at op/stat.t line 103 # Failed test 7 - Link count on hard linked file at op/stat.t line 113 # got "1" # expected "2" # Failed test 86 - negative -A works at op/stat.t line 504 op/stat.t .. Failed 3/113 subtests (less 45 skipped subtests: 65 okay) Test Summary Report ------------------- op/stat.t (Wstat: 0 Tests: 113 Failed: 3) Failed tests: 5, 7, 86 Files=1, Tests=113, 5 wallclock secs ( 0.09 usr + 0.00 sys = 0.09 CPU) Result: FAIL F:\perl\t> -------------------------------------------------- A simple test says Win32::FsType superficially works, but, again, cwd might be a mess in harness/test.pl/other framework parts, or a bug in perlhost layer. -------------------------------------------------- F:\perl\t>perl -I..\lib -E" say Win32::FsType()" FAT6255 F:\perl\t> -------------------------------------------------- Due to me being low on time, I want to get my thoughts out and into the record. This should get a "Known Issues" for 5.20 if nobody investigates and fixes the test fails or fixes core. I got no responses on p5p IRC whether to open new ticket or reply to this. So I reply to this ticket. Someone with ticket privilege needs to change this ticket to open. Also this ticket should be renamed to "core tests fail when built on FAT drive with Win32 OS on NTFS drive", since "some tests fail" is a horrible title for this ticket. -- bulk88 ~ bulk88 at hotmail.com
RT-Send-CC: perl5-porters [...] perl.org
Re-opening at the request of bulk88 -- Karl Williamson
Subject: Re: [perl #21442] core tests fail when built on FAT drive with Win32 OS on NTFS drive
CC: perl5-porters [...] perl.org
Date: Mon, 3 Mar 2014 19:56:49 +0000
To: bulk88 via RT <perlbug-followup [...] perl.org>
From: Nicholas Clark <nick [...] ccl4.org>
Download (untitled) / with headers
text/plain 602b
On Mon, Mar 03, 2014 at 11:49:54AM -0800, bulk88 via RT wrote: Show quoted text
> On Tue Jul 03 00:06:38 2012, doy wrote:
> > Closing, since it doesn't appear that we have been able to reproduce this. > > > > -doy
> > Someone with ticket privilege needs to change this ticket to open, see last paragraph of this post for details.
I've re-opened it (which is fast, as I'm logged in) Sorry, I don't have time to figure out anything useful to say about the rest of the message (which I've skimmed) other than thanks for figuring out the cause of the bug. It's not clear that there's an "obvious" fix. Nicholas Clark
From: Brian Fraser <fraserbn [...] gmail.com>
To: Brian Fraser via RT <perlbug-followup [...] perl.org>
Date: Mon, 3 Mar 2014 21:18:51 +0100
Subject: Re: [perl #21442] core tests fail when built on FAT drive with Win32 OS on NTFS drive
CC: Perl5 Porters Mailing List <perl5-porters [...] perl.org>
Download (untitled) / with headers
text/plain 12.3k
Download (untitled) / with headers
text/html 13.9k
On Mon, Mar 3, 2014 at 8:49 PM, bulk88 via RT <perlbug-followup@perl.org> wrote:
Show quoted text
On Tue Jul 03 00:06:38 2012, doy wrote:
> Closing, since it doesn't appear that we have been able to reproduce this.
>
> -doy

Someone with ticket privilege needs to change this ticket to open, see last paragraph of this post for details.

I previously was not able to reproduce this when I last looked at this ticket, but by chance, I got a nearly identical test fail list on 5.19 blead to the OP from 2003. This is how to reproduce it. The Windows OS drive is NTFS, but you build Perl on FAT32 or FAT16. 1 Mechanical HD with Win OS on NTFS and 2nd FAT32 partition or usb stick with FAT16 made these failures for me.


FAT32 build drive, OS on NTFS. OS is NOT on C: drive here.
---------------------------------------------------------
C:\perl519\src\t>  ..\perl.exe -I..\lib op/stat.t
1..113
ok 1 - nlink on regular file
ok 2 # skip mtime and ctime not reliable
ok 3 # skip mtime and ctime not reliable
ok 4 - link() implemented
not ok 5 - linked tmp testfile
# Failed test 5 - linked tmp testfile at op/stat.t line 103
ok 6 - chmoded tmp testfile
not ok 7 - Link count on hard linked file
# Failed test 7 - Link count on hard linked file at op/stat.t line 113
#      got "1"
# expected "2"
ok 8 # skip No ctime concept on this OS
ok 9 # skip No ctime concept on this OS
ok 10 - -z on empty filehandle
ok 11 -    and -s
ok 12 - -z on empty file
ok 13 -    and -s
ok 14 - -z on empty filehandle
ok 15 -    and -s
ok 16 - -z on non-empty file
ok 17 -    and -s
ok 18 - chmod 0000
ok 19 # skip Can't test -r or -w meaningfully if you're superuser
ok 20 # skip Can't test -r or -w meaningfully if you're superuser
ok 21 -    -x
ok 22 - chmod 0700
ok 23 -    -r
ok 24 -    -w
ok 25 # skip -x simply determines if a file ends in an executable suffix
ok 26 -    -f
ok 27 -    !-d
ok 28 - -d cwd
ok 29 - !-f cwd
ok 30 # skip symlink not implemented
ok 31 # skip symlink not implemented
ok 32 # skip symlink not implemented
ok 33 - -o
ok 34 - -e
ok 35 -    -e on unlinked file
ok 36 # skip No character, socket or block special files
ok 37 # skip No character, socket or block special files
ok 38 # skip No character, socket or block special files
ok 39 # skip No character, socket or block special files
ok 40 # skip No character, socket or block special files
ok 41 # skip No character, socket or block special files
ok 42 # skip Can't find a setuid file to test with
ok 43 # skip Can't find a setuid file to test with
ok 44 # skip Can't find a setuid file to test with
ok 45 # skip Test uses unixisms
ok 46 # skip Test uses unixisms
ok 47 - !-t on closed TTY filehandle
ok 48 - -t on STDIN
ok 49 # skip No null device to test with
ok 50 - -T
ok 51 - !-B
ok 52 - -B
ok 53 - !-T
ok 54 - -T on filehandle causes no errors
ok 55 -    -T
ok 56 -    !-B
ok 57 - after readline
ok 58 -    still -T
ok 59 -    still -B
ok 60 - reopened and after readline
ok 61 -    still -T
ok 62 -    still !-B
ok 63 - after seek
ok 64 -    still -T
ok 65 -    still !-B
ok 66 - at EOF
ok 67 -    still -T
ok 68 -    now -B
ok 69 # skip No null device to test with
ok 70 # skip No null device to test with
ok 71 - bare -f   uses $_
ok 72 -      -f() "
ok 73 - stat returns full 13 elements
ok 74 - lstat _ croaks after stat
ok 75 - lstat *_ croaks after stat
ok 76 - lstat \*_ croaks after stat
ok 77 - -l _ croaks after stat
ok 78 - lstat _ ok after lstat
ok 79 - -l _ ok after lstat
ok 80 - stat $ioref resets stat type
ok 81 - lstat $ioref reverts to regular fstat
ok 82 # skip No lstat
ok 83 # skip No lstat
# Zzz...
ok 84 - can create tmp file
# time=1393701938, stat=(2 0 33206 1 0 0 2 0 1393650000 1393701944 1393701943  )

# -MAC=(-6.94444444444444e-005 0.601134259259259 -5.78703703703704e-005)
ok 85 - negative -M works
not ok 86 - negative -A works
# Failed test 86 - negative -A works at op/stat.t line 504
ok 87 - negative -C works
ok 88 - unlink tmp file
ok 89 - can create temp file
ok 90 - -T _ doesn't break the statbuffer
ok 91 # skip No lstat
ok 92 # skip No dirfd()
ok 93 # skip No dirfd()
ok 94 # skip No dirfd()
ok 95 # skip No dirfd()
ok 96 # skip No dirfd()
ok 97 # skip No dirfd()
ok 98 # skip No dirfd()
ok 99 # skip No dirfd()
ok 100 # skip No dirfd()
ok 101 - can create temp file
ok 102 - stat(*F{IO}) works
ok 103 - single file tests work with *F{IO}
ok 104 # skip No dirfd()
ok 105 # skip No dirfd()
ok 106 # skip No dirfd()
ok 107 # skip No dirfd()
ok 108 # skip No dirfd()
ok 109 # skip No dirfd()
ok 110 # skip No dirfd()
ok 111 # skip No dirfd()
ok 112 # skip No dirfd()
ok 113 - no unopened warning from stat _


C:\perl519\src\t>  ..\perl.exe -I..\lib io/fs.t
1..55
ok 1 # skip bogus umask
not ok 2 - link a b
# Failed test 2 - link a b at io/fs.t line 101
not ok 3 - link b c
# Failed test 3 - link b c at io/fs.t line 102
not ok 4 - link count of triply-linked file
# Failed test 4 - link count of triply-linked file at io/fs.t line 112
#      got undef
# expected "3"
not ok 5 - mode of triply-linked file
# Failed test 5 - mode of triply-linked file at io/fs.t line 122
#      got "00"
# expected "0666"
ok 6 - chmod succeeding
not ok 7 - chmod going through
# Failed test 7 - chmod going through at io/fs.t line 142
#      got "0"
# expected "292"
not ok 8 - chmod two files
# Failed test 8 - chmod two files at io/fs.t line 149
#      got "1"
# expected "2"
not ok 9 - chmod going through to c
# Failed test 9 - chmod going through to c at io/fs.t line 157
#      got "0"
# expected "438"
ok 10 - chmod going through to x
not ok 11 - unlink two files
# Failed test 11 - unlink two files at io/fs.t line 169
#      got "1"
# expected "2"
ok 12 - ino of removed file b should be undef
ok 13 - ino of removed file x should be undef
ok 14 # skip no fchmod
ok 15 # skip no fchmod
ok 16 # skip no fchmod
ok 17 # skip no fchmod
ok 18 # skip no fchmod
ok 19 # skip no fchown
ok 20 - fchmod is unimplemented
ok 21 - fchown is unimplemented
ok 22 - rename a b
ok 23 - ino of renamed file a should be undef
ok 24 - utime
ok 25 # skip bogus inode num
ok 26 # skip filesystem atime/mtime granularity too low
ok 27 # skip filesystem atime/mtime granularity too low
# utime undef, undef --> 1393650000, 1393714698
ok 28 - atime
ok 29 - mtime
ok 30 # skip no futimes
ok 31 # skip no futimes
ok 32 # skip no futimes
ok 33 # skip no futimes
ok 34 - futimes is unimplemented
ok 35 - unlink b
ok 36 - ino of unlinked file b should be undef
ok 37 # skip No symbolic links found to test with
ok 38 # skip No symbolic links found to test with
ok 39 - truncation to five bytes
ok 40 - truncation to zero bytes
ok 41 - fh resize to 200
ok 42 - fh resize to 200 working (filename check)
ok 43 - fh resize to zero
ok 44 - fh resize to zero working (filename check)
ok 45 - fh resize by IO slot
ok 46 - fh resize by IO slot working
ok 47 - truncate(word) does not fall back to file name
ok 48 - rename working
ok 49 - rename on directories
ok 50 - rename on directories working
ok 51 - extend sp in pp_chmod
ok 52 - extend sp in pp_chown
ok 53 - can't unlink directory without -U and privileges
ok 54 - unlink directory without -U sets errno
ok 55 - unlink non-existent directory without -U sets ENOENT
------------------------------------------------------
building perl on usb stick (F: drive)
------------------------------------------------------
usb stick
-------------------
../lib/vmsish.t ................................................... ok
../lib/warnings.t ................................................. ok
x2p/find2perl.t ................................................... skipped: Nee
d something vaguely POSIX
x2p/s2p.t ......................................................... ok

Test Summary Report
-------------------
io/fs.t                                                         (Wstat: 0 Tests:
 55 Failed: 8)
  Failed tests:  2-5, 7-9, 11
op/stat.t                                                       (Wstat: 0 Tests:
 113 Failed: 3)
  Failed tests:  5, 7, 86
Files=2407, Tests=691806, 17365 wallclock secs (142.05 usr +  6.55 sys = 148.59
CPU)
Result: FAIL
NMAKE : fatal error U1077: '..\perl.exe' : return code '0xb'
Stop.

F:\perl\win32>
-------------------------------------------------------

I didn't step it or write additional code, so this analysis may be shoddy. The problem with io/fs.t is this check
----------------------------------------------------
if (defined &Win32::IsWinNT && Win32::IsWinNT()) {
    if (Win32::FsType() eq 'NTFS') {
        $has_link            = 1;
        $accurate_timestamps = 1;
    }
}
----------------------------------------------------

Win32::FsType's docs are
----------------------------------------------------
Win32::FsType()

    [CORE] Returns the name of the filesystem of the currently active drive (like 'FAT' or 'NTFS'). In list context it returns three values: (FSTYPE, FLAGS, MAXCOMPLEN). FSTYPE is the filesystem type as before. FLAGS is a combination of values of the following table:
----------------------------------------------------
"currently active drive" is the problem. There is probably something to do with that code not working right.

----------------------------------------------------
F:\perl\win32>cd ..\t

F:\perl\t>perl -I..\lib harness io/fs.t
io/fs.t .. # Failed test 2 - link a b at io/fs.t line 101
# Failed test 3 - link b c at io/fs.t line 102
# Failed test 4 - link count of triply-linked file at io/fs.t line 112
#      got undef
# expected "3"
# Failed test 5 - mode of triply-linked file at io/fs.t line 122
#      got "00"
# expected "0666"
# Failed test 7 - chmod going through at io/fs.t line 142
#      got "0"
# expected "292"
# Failed test 8 - chmod two files at io/fs.t line 149
#      got "1"
# expected "2"
# Failed test 9 - chmod going through to c at io/fs.t line 157
#      got "0"
# expected "438"
# Failed test 11 - unlink two files at io/fs.t line 169
#      got "1"
# expected "2"
io/fs.t .. Failed 8/55 subtests
        (less 16 skipped subtests: 31 okay)

Test Summary Report
-------------------
io/fs.t (Wstat: 0 Tests: 55 Failed: 8)
  Failed tests:  2-5, 7-9, 11
Files=1, Tests=55,  3 wallclock secs ( 0.08 usr +  0.02 sys =  0.09 CPU)
Result: FAIL

F:\perl\t>
F:\perl\t>perl -I..\lib harness op/stat.t
op/stat.t .. # Failed test 5 - linked tmp testfile at op/stat.t line 103
# Failed test 7 - Link count on hard linked file at op/stat.t line 113
#      got "1"
# expected "2"
# Failed test 86 - negative -A works at op/stat.t line 504
op/stat.t .. Failed 3/113 subtests
        (less 45 skipped subtests: 65 okay)

Test Summary Report
-------------------
op/stat.t (Wstat: 0 Tests: 113 Failed: 3)
  Failed tests:  5, 7, 86
Files=1, Tests=113,  5 wallclock secs ( 0.09 usr +  0.00 sys =  0.09 CPU)
Result: FAIL

F:\perl\t>
--------------------------------------------------

A simple test says Win32::FsType superficially works, but, again, cwd might be a mess in harness/test.pl/other framework parts, or a bug in perlhost layer.
--------------------------------------------------
F:\perl\t>perl -I..\lib -E" say Win32::FsType()"
FAT6255

F:\perl\t>
--------------------------------------------------

Due to me being low on time, I want to get my thoughts out and into the record. This should get a "Known Issues" for 5.20 if nobody investigates and fixes the test fails or fixes core. I got no responses on p5p IRC whether to open new ticket or reply to this. So I reply to this ticket. Someone with ticket privilege needs to change this ticket to open. Also this ticket should be renamed to "core tests fail when built on FAT drive with Win32 OS on NTFS drive", since "some tests fail" is a horrible title for this ticket.

To add to this, those tests (and some others from POSIX.pm) also fail on Android if the underlying fs is FAT, so a more portable solution might be warranted.
(For those wondering: the internal memory of some android devices is occasionally formatted as FAT, and as far as I know, /mnt/sdcard is *always* FAT)


RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 19.1k

Message body is not shown because it is too large.

RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 341b
Here is a patch for io/fs.t failing. op/stat.t needs responses from the ML before I can decide if I can do something about it. Also a perldelta will be needed. I guess it will be part of op/stat.t since this ticket will stay open even after this patch was applied due to the unresolved op/stat.t failures. -- bulk88 ~ bulk88 at hotmail.com
Subject: 0001-perl-21442-fix-fs.t-failures-on-Win32-FAT-drive.patch
From 59e95818283c359852c6adf8c335695c2f159e40 Mon Sep 17 00:00:00 2001 From: bulk88 <bulk88@hotmail.com> Date: Wed, 5 Mar 2014 07:42:21 -0500 Subject: [PATCH] [perl #21442] fix fs.t failures on Win32 FAT drive See ticket for details. This commit does not fix all issues in #21442. --- t/io/fs.t | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/t/io/fs.t b/t/io/fs.t index 78d22e2..5e82b45 100644 --- a/t/io/fs.t +++ b/t/io/fs.t @@ -44,6 +44,9 @@ if (defined &Win32::IsWinNT && Win32::IsWinNT()) { $has_link = 1; $accurate_timestamps = 1; } + else { + $has_link = 0; + } } my $needs_fh_reopen = -- 1.7.9.msysgit.0
RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 401b
On Wed Mar 05 04:47:12 2014, bulk88 wrote: Show quoted text
> Here is a patch for io/fs.t failing. op/stat.t needs responses from > the ML before I can decide if I can do something about it. Also a > perldelta will be needed. I guess it will be part of op/stat.t since > this ticket will stay open even after this patch was applied due to > the unresolved op/stat.t failures.
Bump. -- bulk88 ~ bulk88 at hotmail.com
RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 537b
On Wed Mar 05 04:47:12 2014, bulk88 wrote: Show quoted text
> Here is a patch for io/fs.t failing. op/stat.t needs responses from > the ML before I can decide if I can do something about it. Also a > perldelta will be needed. I guess it will be part of op/stat.t since > this ticket will stay open even after this patch was applied due to > the unresolved op/stat.t failures.
Attached is a patch for the t/op/stat.t failure. This only avoids the failure on MSWin32, and doesn't try to avoid the failure if you test on FAT on say darwin or Linux. Tony
Subject: 0001-perl-21442-skip-link-tests-where-the-filesystem-does.patch
From 659e10a2a275d0b04b04f86c1c8f2aef1a54feee Mon Sep 17 00:00:00 2001 From: Tony Cook <tony@develop-help.com> Date: Wed, 26 Mar 2014 11:35:48 +1100 Subject: [PATCH] [perl #21442] skip link() tests where the filesystem doesn't support them --- t/op/stat.t | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/t/op/stat.t b/t/op/stat.t index 91ce396..b325c56 100644 --- a/t/op/stat.t +++ b/t/op/stat.t @@ -93,6 +93,7 @@ close(FOO); sleep 2; +my $ERROR_INVALID_FUNCTION = 1; # win32 error code SKIP: { unlink $tmpfile_link; @@ -100,6 +101,12 @@ SKIP: { skip "link() unimplemented", 6 if $@ =~ /unimplemented/; is( $@, '', 'link() implemented' ); + + if ($tmpfile_link && + ($^O eq "MSWin32" && $^E == $ERROR_INVALID_FUNCTION)) { + skip "link() not available on this filesystem", 5 + } + ok( $lnk_result, 'linked tmp testfile' ); ok( chmod(0644, $tmpfile), 'chmoded tmp testfile' ); -- 1.7.4.msysgit.0
RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 691b
On Tue Mar 25 17:46:18 2014, tonyc wrote: Show quoted text
> On Wed Mar 05 04:47:12 2014, bulk88 wrote:
> > Here is a patch for io/fs.t failing. op/stat.t needs responses from > > the ML before I can decide if I can do something about it. Also a > > perldelta will be needed. I guess it will be part of op/stat.t since > > this ticket will stay open even after this patch was applied due to > > the unresolved op/stat.t failures.
> > Attached is a patch for the t/op/stat.t failure. > > This only avoids the failure on MSWin32, and doesn't try to avoid the > failure if you test on FAT on say darwin or Linux. > > Tony
So when will these things start getting commited? -- bulk88 ~ bulk88 at hotmail.com
From: Tony Cook <tony [...] develop-help.com>
CC: perl5-porters [...] perl.org
Subject: Re: [perl #21442] core tests fail when built on FAT drive with Win32 OS on NTFS drive
Date: Fri, 4 Apr 2014 17:46:58 +1100
To: bulk88 via RT <perlbug-followup [...] perl.org>
Download (untitled) / with headers
text/plain 849b
On Thu, Apr 03, 2014 at 11:23:49PM -0700, bulk88 via RT wrote: Show quoted text
> On Tue Mar 25 17:46:18 2014, tonyc wrote:
> > On Wed Mar 05 04:47:12 2014, bulk88 wrote:
> > > Here is a patch for io/fs.t failing. op/stat.t needs responses from > > > the ML before I can decide if I can do something about it. Also a > > > perldelta will be needed. I guess it will be part of op/stat.t since > > > this ticket will stay open even after this patch was applied due to > > > the unresolved op/stat.t failures.
> > > > Attached is a patch for the t/op/stat.t failure. > > > > This only avoids the failure on MSWin32, and doesn't try to avoid the > > failure if you test on FAT on say darwin or Linux. > > > > Tony
> > So when will these things start getting commited?
Next week, I'm testing other FAT on Win32 fixes, and until last night it was slow (USB2). Tony
RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 2.3k
On Thu Apr 03 23:47:37 2014, tonyc wrote: Show quoted text
> On Thu, Apr 03, 2014 at 11:23:49PM -0700, bulk88 via RT wrote:
> > On Tue Mar 25 17:46:18 2014, tonyc wrote:
> > > On Wed Mar 05 04:47:12 2014, bulk88 wrote:
> > > > Here is a patch for io/fs.t failing. op/stat.t needs responses from > > > > the ML before I can decide if I can do something about it. Also a > > > > perldelta will be needed. I guess it will be part of op/stat.t since > > > > this ticket will stay open even after this patch was applied due to > > > > the unresolved op/stat.t failures.
> > > > > > Attached is a patch for the t/op/stat.t failure. > > > > > > This only avoids the failure on MSWin32, and doesn't try to avoid the > > > failure if you test on FAT on say darwin or Linux. > > > > > > Tony
> > > > So when will these things start getting commited?
> > Next week, I'm testing other FAT on Win32 fixes, and until last night > it was slow (USB2).
Out of the box I currently get these failures on FAT32: Test Summary Report ------------------- io/fs.t (Wstat: 0 Tests: 55 Failed: 8) Failed tests: 2-5, 7-9, 11 op/stat.t (Wstat: 0 Tests: 113 Failed: 3) Failed tests: 5, 7, 86 win32/fs.t (Wstat: 0 Tests: 4 Failed: 1) Failed test: 4 Files=2407, Tests=690430, 3901 wallclock secs (50.70 usr + 10.59 sys = 61.29 CPU) Result: FAIL With the two patches from above, io/fs.t is now ok, but op/stat.t still fails test 86, and win32/fs.t hasn't been addressed: K:\perl\t>..\perl harness -v op\stat.t [...] ok 82 # skip No lstat ok 83 # skip No lstat # Zzz... ok 84 - can create tmp file # time=1396912752, stat=(10 0 33206 1 0 0 10 0 1396911600 1396912758 1396912757 ) # -MAC=(-6.94444444444444e-005 0.0133333333333333 -5.78703703703704e-005) ok 85 - negative -M works not ok 86 - negative -A works ok 87 - negative -C works ok 88 - unlink tmp file ok 89 - can create temp file ok 90 - -T _ doesn't break the statbuffer [...] K:\perl\t>..\perl harness -v win32\fs.t win32/fs.t .. # Failed test 4 - check for EEXIST at win32/fs.t line 28 # got "22" # expected "17" 1..4 ok 1 - Cannot link to unknown file ok 2 - check errno is ENOENT ok 3 - Cannot link to existing file not ok 4 - check for EEXIST Failed 1/4 subtests
RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 2.4k
On Thu Apr 03 23:47:37 2014, tonyc wrote: Show quoted text
> On Thu, Apr 03, 2014 at 11:23:49PM -0700, bulk88 via RT wrote:
> > On Tue Mar 25 17:46:18 2014, tonyc wrote:
> > > On Wed Mar 05 04:47:12 2014, bulk88 wrote:
> > > > Here is a patch for io/fs.t failing. op/stat.t needs responses from > > > > the ML before I can decide if I can do something about it. Also a > > > > perldelta will be needed. I guess it will be part of op/stat.t since > > > > this ticket will stay open even after this patch was applied due to > > > > the unresolved op/stat.t failures.
> > > > > > Attached is a patch for the t/op/stat.t failure. > > > > > > This only avoids the failure on MSWin32, and doesn't try to avoid the > > > failure if you test on FAT on say darwin or Linux. > > > > > > Tony
> > > > So when will these things start getting commited?
> > Next week, I'm testing other FAT on Win32 fixes, and until last night > it was slow (USB2). > > Tony >
No failures on smoke-me/tonyc/fatfix ---------------------------------------- ../lib/vars.t ..................................................... ok ../lib/vars_carp.t ................................................ ok ../lib/vmsish.t ................................................... ok ../lib/warnings.t ................................................. ok x2p/find2perl.t ................................................... skipped: Nee d something vaguely POSIX x2p/s2p.t ......................................................... ok Test Summary Report ------------------- ../cpan/IPC-Cmd/t/01_IPC-Cmd.t (Wstat: 256 Test s: 459 Failed: 1) Failed test: 141 Non-zero exit status: 1 ../dist/lib/t/01lib.t (Wstat: 1280 Tes ts: 13 Failed: 0) Non-zero exit status: 5 Files=2407, Tests=690383, 3494 wallclock secs (82.97 usr + 4.73 sys = 87.70 CPU ) Result: FAIL NMAKE : fatal error U1077: '..\perl.exe' : return code '0x1' Stop. F:\perl\win32>cd ..\t F:\perl\t>perl harness ../cpan/IPC-Cmd/t/01_IPC-Cmd.t ../cpan/IPC-Cmd/t/01_IPC-Cmd.t .. ok All tests successful. Files=1, Tests=459, 2 wallclock secs ( 0.05 usr + 0.02 sys = 0.06 CPU) Result: PASS F:\perl\t>perl -I..\lib harness ../cpan/IPC-Cmd/t/01_IPC-Cmd.t ../cpan/IPC-Cmd/t/01_IPC-Cmd.t .. ok All tests successful. Files=1, Tests=459, 3 wallclock secs ( 0.03 usr + 0.00 sys = 0.03 CPU) Result: PASS F:\perl\t> ---------------------------------------- -- bulk88 ~ bulk88 at hotmail.com
CC: "perl5-porters [...] perl.org" <perl5-porters [...] perl.org>
Subject: Re: [perl #21442] core tests fail when built on FAT drive with Win32 OS on NTFS drive
To: Tony Cook via RT <perlbug-followup [...] perl.org>
Date: Wed, 9 Apr 2014 00:28:20 +0100
From: Steve Hay <steve.m.hay [...] googlemail.com>
Download (untitled) / with headers
text/plain 2.6k
On 8 April 2014 00:20, Steve Hay via RT <perlbug-followup@perl.org> wrote: Show quoted text
> On Thu Apr 03 23:47:37 2014, tonyc wrote:
>> On Thu, Apr 03, 2014 at 11:23:49PM -0700, bulk88 via RT wrote:
>> > On Tue Mar 25 17:46:18 2014, tonyc wrote:
>> > > On Wed Mar 05 04:47:12 2014, bulk88 wrote:
>> > > > Here is a patch for io/fs.t failing. op/stat.t needs responses from >> > > > the ML before I can decide if I can do something about it. Also a >> > > > perldelta will be needed. I guess it will be part of op/stat.t since >> > > > this ticket will stay open even after this patch was applied due to >> > > > the unresolved op/stat.t failures.
>> > > >> > > Attached is a patch for the t/op/stat.t failure. >> > > >> > > This only avoids the failure on MSWin32, and doesn't try to avoid the >> > > failure if you test on FAT on say darwin or Linux. >> > > >> > > Tony
>> > >> > So when will these things start getting commited?
>> >> Next week, I'm testing other FAT on Win32 fixes, and until last night >> it was slow (USB2).
> > Out of the box I currently get these failures on FAT32: > > Test Summary Report > ------------------- > io/fs.t (Wstat: 0 Tests: 55 Failed: 8) > Failed tests: 2-5, 7-9, 11 > op/stat.t (Wstat: 0 Tests: 113 Failed: 3) > Failed tests: 5, 7, 86 > win32/fs.t (Wstat: 0 Tests: 4 Failed: 1) > Failed test: 4 > Files=2407, Tests=690430, 3901 wallclock secs (50.70 usr + 10.59 sys = 61.29 CPU) > Result: FAIL > > With the two patches from above, io/fs.t is now ok, but op/stat.t still fails test 86, and win32/fs.t hasn't been addressed: > > K:\perl\t>..\perl harness -v op\stat.t > [...] > ok 82 # skip No lstat > ok 83 # skip No lstat > # Zzz... > ok 84 - can create tmp file > # time=1396912752, stat=(10 0 33206 1 0 0 10 0 1396911600 1396912758 1396912757 ) > # -MAC=(-6.94444444444444e-005 0.0133333333333333 -5.78703703703704e-005) > ok 85 - negative -M works > not ok 86 - negative -A works > ok 87 - negative -C works > ok 88 - unlink tmp file > ok 89 - can create temp file > ok 90 - -T _ doesn't break the statbuffer > [...] > > K:\perl\t>..\perl harness -v win32\fs.t > win32/fs.t .. # Failed test 4 - check for EEXIST at win32/fs.t line 28 > # got "22" > # expected "17" > > 1..4 > ok 1 - Cannot link to unknown file > ok 2 - check errno is ENOENT > ok 3 - Cannot link to existing file > not ok 4 - check for EEXIST > Failed 1/4 subtests >
I hadn't noticed the smoke-me/tonyc/fatfix branch then, but having tried it now I find (as bulk88 did) that all tests now pass (or skip).
RT-Send-CC: perl5-porters [...] perl.org
Download (untitled) / with headers
text/plain 348b
On Tue Apr 08 16:28:46 2014, shay wrote: Show quoted text
> I hadn't noticed the smoke-me/tonyc/fatfix branch then, but having > tried it now I find (as bulk88 did) that all tests now pass (or skip).
Thanks Steve, bulk88. Pushed as 58a5e53e67093ffbcd1d4e5f962f2a2f8ebf4172, 3420f3f509a0c431d3fca0ab9e77790cc7fac1ab, e08070a001d506ba49ada1c38161255f2d1bdf06. Tony


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

For issues related to this RT instance (aka "perlbug"), please contact perlbug-admin at perl.org