p5-file-path: upgrade to 2.09, add 5.18 5.20; tests fail

[mojca (Mojca Miklavec)]

When trying to upgrade p5-file-path I'm unable to get the tests to pass.

[dbevans (David B. Evans)]

Not sure what problems you are seeing but tests work for me

DEBUG: Executing command line:  cd "/opt/local/var/macports/build/_opt_macports_trunk_dports_perl_p5-file-path/p5.20-file-path/work/File-Path-2.09" && /usr/bin/make test 
PERL_DL_NONLAZY=1 /opt/local/bin/perl5.20 "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/Path.t ... ok
t/pod.t .... skipped: PERL_AUTHOR_TESTING environment variable not set (or zero)
t/taint.t .. ok
All tests successful.
Files=3, Tests=135,  1 wallclock secs ( 0.04 usr  0.01 sys +  0.12 cusr  0.03 csys =  0.20 CPU)
Result: PASS

[mojca (Mojca Miklavec)]

--->  Testing p5.20-file-path
PERL_DL_NONLAZY=1 /opt/local/bin/perl5.20 "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/Path.t ... 
Failed 124/129 subtests 
t/pod.t .... skipped: PERL_AUTHOR_TESTING environment variable not set (or zero)
t/taint.t .. ok

Test Summary Report
-------------------
t/Path.t (Wstat: 11 Tests: 5 Failed: 0)
  Non-zero wait status: 11
  Parse errors: Bad plan.  You planned 129 tests but ran 5.
Files=3, Tests=11,  1 wallclock secs ( 0.05 usr  0.02 sys +  0.16 cusr  0.13 csys =  0.36 CPU)
Result: FAIL
Failed 1/3 test programs. 0/11 subtests failed.
make: *** [test_dynamic] Error 255
Command failed:  cd "/path/to/p5.20-file-path/work/File-Path-2.09" && /usr/bin/make test 
Exit code: 2

I'm still on the ancient 10.7. How can I debug this?

[mojca (Mojca Miklavec)]

If I comment out line 24 in t/Path.t then all the tests pass:

chmod $perm, "mhx", $path;

where $perm equals 0111 (no read permissions).

If I run the tests as root (cd /path/to/t && make test) then the tests succeed.

This might be connected with the macports user and its permissions. I don't know what permission 111 is good for anyway.

[dbevans (David B. Evans)]

It's just part of the test. At any rate, I think you're right its a permissions problem and the tests would normally be run as root anyway.

sudo port -d test p5.20-file-path

So I would rate this as a pass.

If you want to see which subtest is failing (with comments) run t/Path.t directly

cd work/File-Path-2.09
sudo p5.20 t/Path.t

[dbevans (David B. Evans)]

If I run the test directly without root permission

perl5.20 t/Path.t
1..129
ok 1 - use Cwd;
ok 2 - use File::Path;
ok 3 - use File::Spec::Functions;
mkdir mhx: Permission denied at t/Path.t line 23.
Use of chdir('') or chdir(undef) as chdir() is deprecated at t/Path.t line 654.
ok 4 - ... now chdir 
No root path(s) specified
 at t/Path.t line 655.
not ok 5 - ... and finally rmtree 
#   Failed test '... and finally rmtree '
#   at t/Path.t line 655.
# Looks like you planned 129 tests but ran 5.
# Looks like you failed 1 test of 5 run.
# Looks like your test exited with 255 just after 5.

which makes sense since

$ ls -ld .
drwxr-xr-x  17 macports  wheel  578 Jan 10 04:47 .

Only macports (and root) have write access in the working directory.

[dbevans (David B. Evans)]

Committed in r131362 since tests succeed given appropriate permissions.

[mojca (Mojca Miklavec)]

Can you please try the difference between

sudo port -v test p5.20-file-path

and

sudo port -v -t test p5.20-file-path

?

For me the first one works, but the second one doesn't. The problem lies in line 24 as mentioned earlier. But I don't understand what difference the -t parameter could have.

[dbevans (David B. Evans)]

Replying to mojca@…:

Can you please try the difference between

sudo port -v test p5.20-file-path

and

sudo port -v -t test p5.20-file-path

?

For me the first one works, but the second one doesn't. The problem lies in line 24 as mentioned earlier. But I don't understand what difference the -t parameter could have.

I see the same thing but there no real error message that sheds any light on what the issue is. I'm wondering if this isn't an issue with trace mode rather than p5.20-file-path.

Why don't you bring it up for discussion on the devel list and see if anyone can shed some light?