From @bulk88

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.

--
bulk88 ~ bulk88 at hotmail.com

core tests fail when built on FAT drive with Win32 OS on NTFS drive #6348

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions