Bug #82042 for Test-File: failing tests in Windows (Cygwin)

Sun Dec 16 18:26:54 2012 mascip [...] gmail.com - Ticket created

Subject:

failing tests in Windows (Cygwin)

Hello, two test files fail in WinXP, with Perl 5.14.2 installed on Cygwin 1.7.17. Here is the TAP output: $ cpan Test::File CPAN: Storable loaded ok (v2.27) Going to read '/cygdrive/c/Dropbox/.cpan/Metadata' Database was generated on Sun, 16 Dec 2012 14:07:04 GMT Running install for module 'Test::File' Running make for B/BA/BAREFOOT/Test-File-1.34.tar.gz CPAN: Digest::SHA loaded ok (v5.71) CPAN: Compress::Zlib loaded ok (v2.033) Checksum for /cygdrive/c/Dropbox/.cpan/sources/authors/id/B/BA/BAREFOOT/Test-File- 1.34.tar.gz ok CPAN: File::Temp loaded ok (v0.22) CPAN: Parse::CPAN::Meta loaded ok (v1.4401) CPAN: CPAN::Meta loaded ok (v2.112150) CPAN: Module::CoreList loaded ok (v2.49_02) CPAN.pm: Going to build B/BA/BAREFOOT/Test-File-1.34.tar.gz Checking if your kit is complete... Looks good Writing Makefile for Test::File Writing MYMETA.yml and MYMETA.json cp lib/File.pm blib/lib/Test/File.pm Manifying blib/man3/Test::File.3pm BAREFOOT/Test-File-1.34.tar.gz /usr/bin/make -- OK CPAN: YAML loaded ok (v0.84) Running make test /usr/bin/perl.exe "-MTest::Manifest" "-e" "run_t_manifest(0, 'blib/lib', 'blib/arch', )" t/load.t ...................... ok t/pod.t ....................... ok t/pod_coverage.t .............. ok t/normalize.t ................. ok t/dm_skeleton.t ............... 1/19 # MSWin32 t/dm_skeleton.t ............... ok t/win32.t ..................... ok t/obviously_non_multi_user.t .. ok t/test_files.t ................ 1/20 # Failed test at t/test_files.t line 41. # STDOUT is: # not ok 1 - writeable is not readable # # not: # ok 1 - writeable is not readable # # as expected # STDERR is: # # File [writeable] is readable! # # Failed test 'writeable is not readable' # # at t/test_files.t line 40. # # not: # # as expected # Failed test at t/test_files.t line 52. # STDOUT is: # not ok 1 - readable is not writeable # # not: # ok 1 - readable is not writeable # # as expected # STDERR is: # # File [readable] is writeable! # # Failed test 'readable is not writeable' # # at t/test_files.t line 51. # # not: # # as expected t/test_files.t ................ Failed 2/20 subtests t/test_dirs.t ................. ok t/links.t ..................... ok t/link_counts.t ............... ok t/line_counters.t ............. ok t/file_sizes.t ................ ok t/file_contains.t ............. 4/? # Failed test at t/file_contains.t line 42. # STDERR is: # # Failed test 'not_readable contains (?^:(?mx:^ xxxxxxxxxxx $))' # # at t/file_contains.t line 41. # # '' # # doesn't match '(?^:(?mx:^ xxxxxxxxxxx $))' # # not: # # File [not_readable] is not readable! # # /#\s+Failed\ test.*?\n?.*?at\ t\/file_contains\.t line 41.*\n?/ # # as expected # Failed test at t/file_contains.t line 70. # STDOUT is: # ok 1 - not_readable doesn't contain (?^:(?mx:^ xxxxxxxxxxxxxxxxxxxx $)) # # not: # not ok 1 - not_readable doesn't contain (?^:(?mx:^ xxxxxxxxxxxxxxxxxxxx $)) # # as expected # STDERR is: # # not: # # File [not_readable] is not readable! # # /#\s+Failed\ test.*?\n?.*?at\ t\/file_contains\.t line 69.*\n?/ # # as expected # Failed test at t/file_contains.t line 104. # STDOUT is: # not ok 1 - not_readable contains (?^:(?mx:^ xxxxxxxxxxx $)) # not ok 2 - not_readable contains (?^:(?mx:^ xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx $)) # # not: # not ok 1 - not_readable contains (?^:(?mx:^ xxxxxxxxxxx $)) # # as expected # STDERR is: # # Failed test 'not_readable contains (?^:(?mx:^ xxxxxxxxxxx $))' # # at t/file_contains.t line 103. # # '' # # doesn't match '(?^:(?mx:^ xxxxxxxxxxx $))' # # Failed test 'not_readable contains (?^:(?mx:^ xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx $))' # # at t/file_contains.t line 103. # # '' # # doesn't match '(?^:(?mx:^ xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx $))' # # not: # # File [not_readable] is not readable! # # /#\s+Failed\ test.*?\n?.*?at\ t\/file_contains\.t line 103.*\n?/ # # as expected # Failed test at t/file_contains.t line 139. # STDOUT is: # ok 1 - not_readable doesn't contain (?^:(?mx:^ xxxxxxxxxxxxxxxxxxxx $)) # ok 2 - not_readable doesn't contain (?^:(?mx:^ xxxxxxxxxxxxxxxxxxxx $)) # # not: # not ok 1 - not_readable doesn't contain (?^:(?mx:^ xxxxxxxxxxxxxxxxxxxx $)) # # as expected # STDERR is: # # not: # # File [not_readable] is not readable! # # /#\s+Failed\ test.*?\n?.*?at\ t\/file_contains\.t line 138.*\n?/ # # as expected t/file_contains.t ............. Failed 4/24 subtests t/owner.t ..................... ok t/rt/30346.t .................. ok Test Summary Report ------------------- t/test_files.t (Wstat: 0 Tests: 20 Failed: 2) Failed tests: 10, 12 t/file_contains.t (Wstat: 0 Tests: 24 Failed: 4) Failed tests: 9, 13, 18, 23 Files=16, Tests=233, 22 wallclock secs ( 0.38 usr 0.66 sys + 6.28 cusr 11.62 csys = 18.93 CPU) Result: FAIL Failed 2/16 test programs. 6/233 subtests failed. Makefile:851: recipe for target `test_dynamic' failed make: *** [test_dynamic] Error 255 BAREFOOT/Test-File-1.34.tar.gz /usr/bin/make test -- NOT OK //hint// to see the cpan-testers results for installing this module, try: reports BAREFOOT/Test-File-1.34.tar.gz Running make install make test had returned bad status, won't install without force

Sun Dec 23 21:26:28 2012 BAREFOOT [...] cpan.org - Correspondence added

Show quoted text

> Hello, two test files fail in WinXP, with Perl 5.14.2 installed on > Cygwin 1.7.17.

Well, most of those look like failures because a file that was not supposed to be readable was in fact readable. Is this a problem on Cygwin? I do have two PASS reports from CPAN Testers on 5.14.2 on Cygwin, so it doesn't appear to be a problem that affects all Cygwin installations. One idea is that it might depend on what the underlying file system is. Is it possible that you're using an older filesys (e.g. FAT32) that can't make files non-readable? You can see how the tests are trying to create such files by looking in t/setup_common. So it would be the equivalent of something like: open FH, "> not_readable"; close FH; chmod 0200 "not_readable"; If you create a testfile on your system in this way, is it then readable? That is, does something like print "bogus!\n" if -r "not_readable"; perform as expected?

Sun Dec 23 21:26:29 2012 The RT System itself - Status changed from 'new' to 'open'

Thu Jan 10 15:46:59 2013 mascip [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #82042] failing tests in Windows (Cygwin)
Date:	Thu, 10 Jan 2013 20:46:24 +0000
To:	bug-Test-File [...] rt.cpan.org
From:	mascip <mascip [...] gmail.com>

Ok, i finally took the time to research into this. Sorry it took me so long. Files on my system seem to behave correctly. But -r seems to not return the correct result. I created this subroutine to print the permission of a file: sub permission { my $file_path = shift; my $permission = sprintf "%o", (stat $file_path)[2] & 07777; return $permission; } When 'test_files/writeable' is created in setup_common, its permission is initially 644, and it becomes 200 after chmod. So, this part of the test works. The part that doesn't work properly is in the file_not_readable_ok() function in File.pm. I added these lines after my $ok = ... : my $ok = not -r $filename; print '$ok:' . "$ok \n"; print "permission for file $filename: " . permission($filename) . "\n"; which printed: ok: permission for file writeable: 200 which shows that -r 'writeable' returned 1, while the file was not readable. I have no idea why... On 24 December 2012 02:26, Buddy Burden via RT <bug-Test-File@rt.cpan.org>wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=82042 > >

> > Hello, two test files fail in WinXP, with Perl 5.14.2 installed on > > Cygwin 1.7.17.

> > Well, most of those look like failures because a file that was not > supposed to be readable was in fact readable. Is this a problem on > Cygwin? I do have two PASS reports from CPAN Testers on 5.14.2 on > Cygwin, so it doesn't appear to be a problem that affects all Cygwin > installations. > > One idea is that it might depend on what the underlying file system is. > Is it possible that you're using an older filesys (e.g. FAT32) that > can't make files non-readable? > > You can see how the tests are trying to create such files by looking in > t/setup_common. So it would be the equivalent of something like: > > open FH, "> not_readable"; > close FH; > chmod 0200 "not_readable"; > > If you create a testfile on your system in this way, is it then > readable? That is, does something like > > print "bogus!\n" if -r "not_readable"; > > perform as expected? >

Thu Jan 10 18:29:28 2013 BAREFOOT [...] cpan.org - Correspondence added

It sounds to me like something may be up with cygwin, or else it's just a limitation of the underlying file system, as I suggested before. To prove that, try this: Either create a file and make it non-writeable with Perl (see previous comment for some code), or just put some pause in the test file (like a `sleep` with a very long number of seconds or a stop for input like `<STDIN>`). Now use a separate cygwin terminal to do an `ls` on the file and see what it thinks the perms are. Now actually try to read the file (vi or cat or whatever). You _should_ get "Permission denied". Assuming the ls matches what Perl's chmod set it to, but the file is actually readable, I think we can blame cygwin or the underlying file system. If the ls matches the chmod and the file _isn't_ readable, then perhaps there's something wrong with Perl's `-r` on your system. OTOH, if the ls _doesn't_ match the chmod, maybe there's something wrong with Perl's `chmod` on your system. I'm not sure I can figure out a way to pin this on Test::File, however. :-) I'm pretty sure the test is correctly exposing an issue on your system, and letting you know that testing for readability is likely not to be trustworthy. Hopefully that's not something you were going to use anyway. Assuming it's not, you may just need to give up and force install it (or install it via cpanm -n or somesuch). If the lack of reliability for readability testing is going to be a real problem for you, though, you may need to look at trying a different machine, file system, or Perl delivery mechanism (e.g. ActiveState vs Cygwin). Let me know if there's any more info I can provide.

Thu Jan 10 18:30:35 2013 BAREFOOT [...] cpan.org - Status changed from 'open' to 'stalled'

Fri Jan 11 06:56:58 2013 mascip [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #82042] failing tests in Windows (Cygwin)
Date:	Fri, 11 Jan 2013 11:56:21 +0000
To:	bug-Test-File [...] rt.cpan.org
From:	mascip <mascip [...] gmail.com>

ls says that it's not readable, but then i can read it with vi, so it's a Cygwin problem indeed. I was thinking of installing Pinto which uses Test::File, and i have no idea whether it uses the file_not_readable_ok() function. But i realized that Pinto is overkill for my use, so i've "done all this for nothing". I just wanted to try and help debug, as you answered my bug report in a helpful way. But as it's Cygwin not behaving correctly, it was doubly useless. I'm switching back to Linux anyway. Once i find a distro that works properly on my new build... which seems to attract strange bugs. Thank you for your help, and sorry for the time spent. At least, i've learned some things and will spend less time bothering other people in the future. Next time i'll dive into the code and try to understand the proplem myself, before doing a bug report. On 10 January 2013 23:29, Buddy Burden via RT <bug-Test-File@rt.cpan.org>wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=82042 > > > It sounds to me like something may be up with cygwin, or else it's just > a limitation of the underlying file system, as I suggested before. To > prove that, try this: > > Either create a file and make it non-writeable with Perl (see previous > comment for some code), or just put some pause in the test file (like a > `sleep` with a very long number of seconds or a stop for input like > `<STDIN>`). Now use a separate cygwin terminal to do an `ls` on the > file and see what it thinks the perms are. Now actually try to read the > file (vi or cat or whatever). You _should_ get "Permission denied". > > Assuming the ls matches what Perl's chmod set it to, but the file is > actually readable, I think we can blame cygwin or the underlying file > system. If the ls matches the chmod and the file _isn't_ readable, then > perhaps there's something wrong with Perl's `-r` on your system. OTOH, > if the ls _doesn't_ match the chmod, maybe there's something wrong with > Perl's `chmod` on your system. > > I'm not sure I can figure out a way to pin this on Test::File, however. > :-) I'm pretty sure the test is correctly exposing an issue on your > system, and letting you know that testing for readability is likely not > to be trustworthy. Hopefully that's not something you were going to use > anyway. Assuming it's not, you may just need to give up and force > install it (or install it via cpanm -n or somesuch). If the lack of > reliability for readability testing is going to be a real problem for > you, though, you may need to look at trying a different machine, file > system, or Perl delivery mechanism (e.g. ActiveState vs Cygwin). > > Let me know if there's any more info I can provide. >

Fri Jan 11 06:56:59 2013 The RT System itself - Status changed from 'stalled' to 'open'

Fri Jan 11 07:07:18 2013 mascip [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #82042] failing tests in Windows (Cygwin)
Date:	Fri, 11 Jan 2013 12:06:42 +0000
To:	bug-Test-File [...] rt.cpan.org
From:	mascip <mascip [...] gmail.com>

One way to make the test pass in Cygwin could be to use the built-in stat() function like i did, to test for readability and writeability. This would probably work properly on all systems. The question being whether people using Test::File in Cygwin want to be told that a file is readable when - it is actually readable - Cygwin says that it is readable I don't have an opinion, but i guess it's a question you can ask, if you ever get someone reporting the same bug in Cygwin. Have a nice day! On 11 January 2013 11:56, mascip <mascip@gmail.com> wrote: Show quoted text

> ls says that it's not readable, but then i can read it with vi, > so it's a Cygwin problem indeed. > > I was thinking of installing Pinto which uses Test::File, and i have no > idea whether it uses the file_not_readable_ok() function. But i realized > that Pinto is overkill for my use, so i've "done all this for nothing". > I just wanted to try and help debug, as you answered my bug report in a > helpful way. But as it's Cygwin not behaving correctly, it was doubly > useless. > > I'm switching back to Linux anyway. Once i find a distro that works > properly on my new build... which seems to attract strange bugs. > > Thank you for your help, and sorry for the time spent. At least, i've > learned some things and will spend less time bothering other people in the > future. > Next time i'll dive into the code and try to understand the proplem > myself, before doing a bug report. > > > > > On 10 January 2013 23:29, Buddy Burden via RT <bug-Test-File@rt.cpan.org>wrote: >

>> <URL: https://rt.cpan.org/Ticket/Display.html?id=82042 > >> >> It sounds to me like something may be up with cygwin, or else it's just >> a limitation of the underlying file system, as I suggested before. To >> prove that, try this: >> >> Either create a file and make it non-writeable with Perl (see previous >> comment for some code), or just put some pause in the test file (like a >> `sleep` with a very long number of seconds or a stop for input like >> `<STDIN>`). Now use a separate cygwin terminal to do an `ls` on the >> file and see what it thinks the perms are. Now actually try to read the >> file (vi or cat or whatever). You _should_ get "Permission denied". >> >> Assuming the ls matches what Perl's chmod set it to, but the file is >> actually readable, I think we can blame cygwin or the underlying file >> system. If the ls matches the chmod and the file _isn't_ readable, then >> perhaps there's something wrong with Perl's `-r` on your system. OTOH, >> if the ls _doesn't_ match the chmod, maybe there's something wrong with >> Perl's `chmod` on your system. >> >> I'm not sure I can figure out a way to pin this on Test::File, however. >> :-) I'm pretty sure the test is correctly exposing an issue on your >> system, and letting you know that testing for readability is likely not >> to be trustworthy. Hopefully that's not something you were going to use >> anyway. Assuming it's not, you may just need to give up and force >> install it (or install it via cpanm -n or somesuch). If the lack of >> reliability for readability testing is going to be a real problem for >> you, though, you may need to look at trying a different machine, file >> system, or Perl delivery mechanism (e.g. ActiveState vs Cygwin). >> >> Let me know if there's any more info I can provide. >>

> >

Tue Jan 15 15:31:29 2013 mascip [...] gmail.com - Correspondence added

Subject:	Re: [rt.cpan.org #82042] AutoReply: failing tests in Windows (Cygwin)
Date:	Tue, 15 Jan 2013 20:30:30 +0000
To:	bug-Test-File [...] rt.cpan.org
From:	mascip <mascip [...] gmail.com>

If someone ever encounters the same problem with Cygwin, the solution might be here: Cygwin's chmod often doesn't work properly, but can be set up to work properly, as written here in the Cygwin FAQ. http://cygwin.com/faq/faq-nochunks.html#faq.using.chmod<http://stackoverflow.com/questions/357314/file-permissions-in-cygwin-and-mvfs> This information should maybe figure in the perlcygwin documentation, here: http://search.cpan.org/~rjbs/perl-5.16.2/README.cygwin It caused me problems to install other modules too. If-when i have the time, i might write a draft and send it to the maintainer of the perlcygwin page. On 16 December 2012 23:26, Bugs in Test-File via RT < bug-Test-File@rt.cpan.org> wrote: Show quoted text

> > Greetings, > > This message has been automatically generated in response to the > creation of a trouble ticket regarding: > "failing tests in Windows (Cygwin)", > a summary of which appears below. > > There is no need to reply to this message right now. Your ticket has been > assigned an ID of [rt.cpan.org #82042]. Your ticket is accessible > on the web at: > > https://rt.cpan.org/Ticket/Display.html?id=82042 > > Please include the string: > > [rt.cpan.org #82042] > > in the subject line of all future correspondence about this issue. To do > so, > you may reply to this message. > > Thank you, > bug-Test-File@rt.cpan.org > > ------------------------------------------------------------------------- > Hello, two test files fail in WinXP, with Perl 5.14.2 installed on > Cygwin 1.7.17. Here is the TAP output: > > $ cpan Test::File > CPAN: Storable loaded ok (v2.27) > Going to read '/cygdrive/c/Dropbox/.cpan/Metadata' > Database was generated on Sun, 16 Dec 2012 14:07:04 GMT > Running install for module 'Test::File' > Running make for B/BA/BAREFOOT/Test-File-1.34.tar.gz > CPAN: Digest::SHA loaded ok (v5.71) > CPAN: Compress::Zlib loaded ok (v2.033) > Checksum for > /cygdrive/c/Dropbox/.cpan/sources/authors/id/B/BA/BAREFOOT/Test-File- > 1.34.tar.gz ok > CPAN: File::Temp loaded ok (v0.22) > CPAN: Parse::CPAN::Meta loaded ok (v1.4401) > CPAN: CPAN::Meta loaded ok (v2.112150) > CPAN: Module::CoreList loaded ok (v2.49_02) > > CPAN.pm: Going to build B/BA/BAREFOOT/Test-File-1.34.tar.gz > > Checking if your kit is complete... > Looks good > Writing Makefile for Test::File > Writing MYMETA.yml and MYMETA.json > cp lib/File.pm blib/lib/Test/File.pm > Manifying blib/man3/Test::File.3pm > BAREFOOT/Test-File-1.34.tar.gz > /usr/bin/make -- OK > CPAN: YAML loaded ok (v0.84) > Running make test > /usr/bin/perl.exe "-MTest::Manifest" "-e" "run_t_manifest(0, 'blib/lib', > 'blib/arch', )" > t/load.t ...................... ok > t/pod.t ....................... ok > t/pod_coverage.t .............. ok > t/normalize.t ................. ok > t/dm_skeleton.t ............... 1/19 # MSWin32 > t/dm_skeleton.t ............... ok > t/win32.t ..................... ok > t/obviously_non_multi_user.t .. ok > t/test_files.t ................ 1/20 > # Failed test at t/test_files.t line 41. > # STDOUT is: > # not ok 1 - writeable is not readable > # > # not: > # ok 1 - writeable is not readable > # > # as expected > # STDERR is: > # # File [writeable] is readable! > # # Failed test 'writeable is not readable' > # # at t/test_files.t line 40. > # > # not: > # > # as expected > > # Failed test at t/test_files.t line 52. > # STDOUT is: > # not ok 1 - readable is not writeable > # > # not: > # ok 1 - readable is not writeable > # > # as expected > # STDERR is: > # # File [readable] is writeable! > # # Failed test 'readable is not writeable' > # # at t/test_files.t line 51. > # > # not: > # > # as expected > t/test_files.t ................ Failed 2/20 subtests > t/test_dirs.t ................. ok > t/links.t ..................... ok > t/link_counts.t ............... ok > t/line_counters.t ............. ok > t/file_sizes.t ................ ok > t/file_contains.t ............. 4/? > # Failed test at t/file_contains.t line 42. > # STDERR is: > # # Failed test 'not_readable contains (?^:(?mx:^ xxxxxxxxxxx $))' > # # at t/file_contains.t line 41. > # # '' > # # doesn't match '(?^:(?mx:^ xxxxxxxxxxx $))' > # > # not: > # # File [not_readable] is not readable! > # > # /#\s+Failed\ test.*?\n?.*?at\ t\/file_contains\.t line 41.*\n?/ > # > # as expected > > # Failed test at t/file_contains.t line 70. > # STDOUT is: > # ok 1 - not_readable doesn't contain (?^:(?mx:^ xxxxxxxxxxxxxxxxxxxx > $)) > # > # not: > # not ok 1 - not_readable doesn't contain (?^:(?mx:^ > xxxxxxxxxxxxxxxxxxxx $)) > # > # as expected > # STDERR is: > # > # not: > # # File [not_readable] is not readable! > # > # /#\s+Failed\ test.*?\n?.*?at\ t\/file_contains\.t line 69.*\n?/ > # > # as expected > > # Failed test at t/file_contains.t line 104. > # STDOUT is: > # not ok 1 - not_readable contains (?^:(?mx:^ xxxxxxxxxxx $)) > # not ok 2 - not_readable contains (?^:(?mx:^ > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx $)) > # > # not: > # not ok 1 - not_readable contains (?^:(?mx:^ xxxxxxxxxxx $)) > # > # as expected > # STDERR is: > # # Failed test 'not_readable contains (?^:(?mx:^ xxxxxxxxxxx $))' > # # at t/file_contains.t line 103. > # # '' > # # doesn't match '(?^:(?mx:^ xxxxxxxxxxx $))' > # # Failed test 'not_readable contains (?^:(?mx:^ > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx $))' > # # at t/file_contains.t line 103. > # # '' > # # doesn't match '(?^:(?mx:^ > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx $))' > # > # not: > # # File [not_readable] is not readable! > # > # /#\s+Failed\ test.*?\n?.*?at\ t\/file_contains\.t line 103.*\n?/ > # > # as expected > > # Failed test at t/file_contains.t line 139. > # STDOUT is: > # ok 1 - not_readable doesn't contain (?^:(?mx:^ xxxxxxxxxxxxxxxxxxxx > $)) > # ok 2 - not_readable doesn't contain (?^:(?mx:^ xxxxxxxxxxxxxxxxxxxx > $)) > # > # not: > # not ok 1 - not_readable doesn't contain (?^:(?mx:^ > xxxxxxxxxxxxxxxxxxxx $)) > # > # as expected > # STDERR is: > # > # not: > # # File [not_readable] is not readable! > # > # /#\s+Failed\ test.*?\n?.*?at\ t\/file_contains\.t line 138.*\n?/ > # > # as expected > t/file_contains.t ............. Failed 4/24 subtests > t/owner.t ..................... ok > t/rt/30346.t .................. ok > > Test Summary Report > ------------------- > t/test_files.t (Wstat: 0 Tests: 20 Failed: 2) > Failed tests: 10, 12 > t/file_contains.t (Wstat: 0 Tests: 24 Failed: 4) > Failed tests: 9, 13, 18, 23 > Files=16, Tests=233, 22 wallclock secs ( 0.38 usr 0.66 sys + 6.28 cusr > 11.62 csys = 18.93 CPU) > Result: FAIL > Failed 2/16 test programs. 6/233 subtests failed. > Makefile:851: recipe for target `test_dynamic' failed > make: *** [test_dynamic] Error 255 > BAREFOOT/Test-File-1.34.tar.gz > /usr/bin/make test -- NOT OK > //hint// to see the cpan-testers results for installing this module, > try: > reports BAREFOOT/Test-File-1.34.tar.gz > Running make install > make test had returned bad status, won't install without force > >

Bug #82042 for Test-File: failing tests in Windows (Cygwin)

Preferred bug tracker