Re: [rt.cpan.org #121128] Test failures on Cygwin

[email protected] ("Ken Brown via RT")
Newsgroups perl.par
Message-ID <[email protected]>
Sat Apr 15 07:44:44 2017: Request 121128 was acted upon.
Transaction: Correspondence added by [email protected]
       Queue: Module-ScanDeps
     Subject: Re: [rt.cpan.org #121128] Test failures on Cygwin
   Broken in: (no value)
    Severity: (no value)
       Owner: Nobody
  Requestors: [email protected]
      Status: open
 Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=121128 >


On 4/14/2017 7:10 PM, Roderich Schupp via RT wrote:
> Probably harmless.
> But can you patch t/10-case-insensitive-keys.t
>
> ...
> # Functional i/f
> my $rv1 = scan_deps(@roots1);
> #use Data::Dump qw(dump);
> #print dump($rv1), "\n";
> ...
>
> like so:
>
> ...
> # Functional i/f
> my $rv1 = scan_deps(@roots1);
> use Data::Dumper;
> print STDERR "\n", Dumper($rv1);
> ...
>
> then run
>
>   make test TEST_VERBOSE=1 TEST_FILES=t/10-case-insensitive-keys.t
>
> and attach its stdout/stderr.

Attached.

By the way, my file system is set up to be case sensitive, which I guess 
is the same as case_intolerant.  [Cygwin users can control this by a 
registry setting.]  I wonder if the problem is that the File::Spec 
module didn't detect this; shouldn't the test have been skipped?

I don't have time at the moment, but I'll take a look at the File::Spec 
module later and see if that's the issue.

Ken
test_err.log (text/plain, 1.6 KB)
$VAR1 = {
          'Test.pm' => {
                         'key' => 'Test.pm',
                         'type' => 'module',
                         'used_by' => [
                                        'this_case.pl'
                                      ],
                         'file' => '/home/kbrown-admin/.cpan/build/Module-ScanDeps-1.23-nAf8Qz/t/data/case-insensitive-keys/Test.pm'
                       },
          'this_case.pl' => {
                              'file' => '/home/kbrown-admin/.cpan/build/Module-ScanDeps-1.23-nAf8Qz/t/data/case-insensitive-keys/this_case.pl',
                              'type' => 'data',
                              'uses' => [
                                          'Test.pm'
                                        ],
                              'key' => 'this_case.pl'
                            },
          'that_case.pl' => {
                              'file' => '/home/kbrown-admin/.cpan/build/Module-ScanDeps-1.23-nAf8Qz/t/data/case-insensitive-keys/that_case.pl',
                              'type' => 'data',
                              'key' => 'that_case.pl'
                            }
        };
#   Failed test 'For Test.pm: number of used_by in $rv_to_test == Number of used_by in $rv_to_match'
#   at t/10-case-insensitive-keys.t line 57.
#          got: 1
#     expected: 2
#   Failed test 'For that_case.pl: uses exists as expected'
#   at t/10-case-insensitive-keys.t line 57.
# Looks like you planned 43 tests but ran 40.
# Looks like you failed 2 tests of 40 run.
Failed 1/1 test programs. 2/40 subtests failed.
make: *** [Makefile:897: test_dynamic] Error 2
test_out.log (text/plain, 2.9 KB)
PERL_DL_NONLAZY=1 "/usr/bin/perl.exe" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/10-case-insensitive-keys.t
t/10-case-insensitive-keys.t .. 
1..43
ok 1 - use Module::ScanDeps;
ok 2 - $rv is a ref
ok 3 - that_case.pl is in rv
ok 4 - this_case.pl is in rv
ok 5 - For this_case.pl: the sub-key matches
ok 6 - For this_case.pl: the file has been verified
ok 7 - For this_case.pl: the type matches module|autoload|data|shared
ok 8 - used-by not defined so this_case.pl must be one of the input files or is a plugin
ok 9 - $rv contains a matching used_by field for the uses entry Test.pm for key this_case.pl
ok 10 - For that_case.pl: the sub-key matches
ok 11 - For that_case.pl: the file has been verified
ok 12 - For that_case.pl: the type matches module|autoload|data|shared
ok 13 - used-by not defined so that_case.pl must be one of the input files or is a plugin
ok 14 - $rv contains a matching used_by field for the uses entry Test.pm for key that_case.pl
ok 15 - For Test.pm: the sub-key matches
ok 16 - For Test.pm: the file has been verified
ok 17 - For Test.pm: the type matches module|autoload|data|shared
ok 18 - Test.pm's used_by has no duplicates
ok 19 - All entries in Test.pm's used_by are themselves described in $rv
ok 20 - $rv contains a matching uses field for the used_by entry that_case.pl for key Test.pm
ok 21 - $rv contains a matching uses field for the used_by entry this_case.pl for key Test.pm
ok 22 - $rv_to_test is a ref
ok 23 - Number of keys in $rv_to_test == Number of keys in $rv_to_match
ok 24 - Keys in $rv_to_test all eq keys in $rv_to_match
ok 25 - For Test.pm: sub-key matches the expected
ok 26 - For Test.pm: file matches the expected
ok 27 - For Test.pm: type matches the expected
ok 28 - For Test.pm: used_by exists as expected
not ok 29 - For Test.pm: number of used_by in $rv_to_test == Number of used_by in $rv_to_match
ok 30 - For that_case.pl: sub-key matches the expected
ok 31 - For that_case.pl: file matches the expected
ok 32 - For that_case.pl: type matches the expected
not ok 33 - For that_case.pl: uses exists as expected
ok 34 - For this_case.pl: sub-key matches the expected
ok 35 - For this_case.pl: file matches the expected
ok 36 - For this_case.pl: type matches the expected
ok 37 - For this_case.pl: uses exists as expected
ok 38 - For this_case.pl: number of uses in $rv_to_test == Number of uses in $rv_to_match
ok 39 - For this_case.pl: uses in $rv_to_test all eq uses in $rv_to_match
ok 40 - contains only one match
Dubious, test returned 2 (wstat 512, 0x200)
Failed 5/43 subtests 

Test Summary Report
-------------------
t/10-case-insensitive-keys.t (Wstat: 512 Tests: 40 Failed: 2)
  Failed tests:  29, 33
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 43 tests but ran 40.
Files=1, Tests=40,  1 wallclock secs ( 0.03 usr  0.03 sys +  0.16 cusr  0.18 csys =  0.40 CPU)
Result: FAIL
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.