Sat Apr 15 13:14:49 2017: Request 121128 was acted upon.
Transaction: Correspondence added by RSCHUPP
Queue: Module-ScanDeps
Subject: Test failures on Cygwin
Broken in: (no value)
Severity: (no value)
Owner: Nobody
Requestors: kbr...@cornell.edu
Status: open
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=121128 >
On 2017-04-15 07:44:44, kbr...@cornell.edu wrote:
> Attached.
Yep, that is exactly the output you would get when forcing
t/10-case-insensitive-keys.t to run (not skip) on a case-sensitive filesystem.
> By the way, my file system is set up to be case sensitive, which I guess
> is the same as case_intolerant.
:) "case intolerant" sounds like some form of allergy to me
> I wonder if the problem is that the File::Spec
> module didn't detect this; shouldn't the test have been skipped?
I looked at File::Spec::Cygwin (from Perl 5.24.1) and it has indeed a Cygwin
specific
File::Spec::case_tolerant. Sorry, I have no machine to test this, but on
first glance this test looks suspicious since there's no "use Cygwin":
sub case_tolerant {
return 1 unless $^O eq 'cygwin'
and defined &Cygwin::mount_flags;
...
Do the following two oneliners produce different output?
perl -E 'say "DEFINED" if defined &Cygwin::mount_flags'
perl -MCygwin -E 'say "DEFINED" if defined &Cygwin::mount_flags'
Cheers, Roderich
