"peter green" <[EMAIL PROTECTED]> wrote:
> would it be possible to reduce the test to only cause a warning until
> it is worked out what about the build environment is causing the false
> positive?

I think that may be a reasonable thing to do here.  This test is trying
to check that "pwd" can read very long paths, specifically 256 levels of
directories below the test's current directory.   The error message
indicates that it is failing after going 265 levels up (i.e. outside of
the build directory, closer to the root).

The error seems to suggest that lstat() failed, though none of the
documented reasons for failure seem plausible.  Another possibility is
that the filesystem on the buildd is corrupt and one ".." link does not
point to the correct directory.  (Lack of read permission on a directory
is another possibility I thought of, but that results in a different
error message.)

Ben.

-- 
Ben Hutchings
Beware of bugs in the above code;
I have only proved it correct, not tried it. - Donald Knuth

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to