| Subject: | t/cwd.t fails if path to test files is inaccessible |
my cpan directory was in /home/myusername/.cpan/.... When I ran
tests, test 26 failed with a message about abs_path failing.
ok 20 - Cwd::chdir() updates $ENV{PWD}
#/home/myusername/.cpan/build/PathTools-3.31-
ruFSCU/t/_ptrslt_/_path_/_to_/_a_
#/home/myusername/.cpan/build/PathTools-3.31-
ruFSCU/t/_ptrslt_/_path_/_to_
#/home/myusername/.cpan/build/PathTools-3.31-
ruFSCU/t/_ptrslt_/_path_
#/home/myusername/.cpan/build/PathTools-3.31-ruFSCU/t/_ptrslt_
#/home/myusername/.cpan/build/PathTools-3.31-ruFSCU/t
ok 21
ok 22
ok 23
ok 24
not ok 25
# Failed test (t/cwd.t at line 213)
# '/home/myusername/.cpan/build/PathTools-3.31-
ruFSCU/t/linktest'
# doesn't match '(?i-
xsm:\/home\/myusername\/\.cpan\/build\/PathTools\-3\.31\-
ruFSCU\/t\/_ptrslt_\/_path_\/_to_\/_a_\/_dir_$)'
ok 26 - abs_path() can be invoked on a file
ok 27 - fast_abs_path() can be invoked on a file
The actual problem turned out that /home did not have world read
permissions (0751) . The test message didn't really give me any hints as
to why this was happening.
What I'm thinking is that a test is in order prior to this one to verify that
read access is possible all the way up to where the test is running from.
I know this is complicated by Cwd functioning on Windows/VMS.
A hint as to why this was happening was gleaned from RT 13851,
although in this case, _perl_abs_path seems to be what's failing.
I would provide a test case, however I feel like I don't know the code
well enough to advise a test.
Please let me know if you need any more info.
This failure happened on perl 5.8.8 on a CentOS 5 System