All those tests are filesystem-related. Is the filesystem you are building on somehow non-standard?

This is a long shot, since I would expect far more tests to fail if your filesystem were weird, but maybe you are building on a network filesystem (AFS, NFS, ...) which behaves weird.

Other than that, it is weird that only some of the tests that create/check files fail and the basic ones seem to pass.

One thing that comes to mind when looking at ExtUtils::Install/Packlist.t:

        # set this file to read-only
        chmod 0444, 'eplist';
...
        eval { ExtUtils::Packlist::write({}, 'eplist') };

[download]

If you are running the tests as root or some other kind of superuser, the test will pass, as file permissions don't apply to root.

In reply to Re: perl 5.38 - File open test failures on RockyLinux 8.8 by Corion
in thread perl 5.38 - File open test failures on RockyLinux 8.8 by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.