Testing p5.34-fcgi fails because FCGI::Client is not installed

[ballapete (Peter "Pete" Dyballa)]

Can't locate FCGI/Client.pm in @INC (you may need to install the FCGI::Client module) (@INC contains: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5-fcgi/p5.34-fcgi/work/FCGI-0.82/blib/lib /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5-fcgi/p5.34-fcgi/work/FCGI-0.82/blib/arch /opt/local/lib/perl5/site_perl/5.34/darwin-thread-multi-2level /opt/local/lib/perl5/site_perl/5.34 /opt/local/lib/perl5/vendor_perl/5.34/darwin-thread-multi-2level /opt/local/lib/perl5/vendor_perl/5.34 /opt/local/lib/perl5/5.34/darwin-thread-multi-2level /opt/local/lib/perl5/5.34 .) at t/02-unix_domain_socket.t line 6.
BEGIN failed--compilation aborted at t/02-unix_domain_socket.t line 6.

[ballapete (Peter "Pete" Dyballa)]

Main.log from intel macOS Sonoma, 14.6.1

[ballapete (Peter "Pete" Dyballa)]

How can I code test dependencies in Perl Portfiles? p5-file-homedir for example hardcodes the path to Perl in its test files à la #!/usr/bin/perl so that I added at the Portfile's end these lines:

pre-test {
    reinplace "s|/usr/bin/perl|/usr/bin/env perl${perl5.major}|" ${worksrcpath}/t/01_compile.t
    reinplace "s|/usr/bin/perl|/usr/bin/env perl${perl5.major}|" ${worksrcpath}/t/02_main.t
    reinplace "s|/usr/bin/perl|/usr/bin/env perl${perl5.major}|" ${worksrcpath}/t/10_test.t
    reinplace "s|/usr/bin/perl|/usr/bin/env perl${perl5.major}|" ${worksrcpath}/t/11_darwin.t
    reinplace "s|/usr/bin/perl|/usr/bin/env perl${perl5.major}|" ${worksrcpath}/t/12_darwin_carbon.t
    reinplace "s|/usr/bin/perl|/usr/bin/env perl${perl5.major}|" ${worksrcpath}/t/13_darwin_cocoa.t
    reinplace "s|/usr/bin/perl|/usr/bin/env perl${perl5.major}|" ${worksrcpath}/t/20_empty_home.t
}

test.run            yes

At least they patch the test files… (but test still fail)

[ballapete (Peter "Pete" Dyballa)]

The issue is being tracked here: ​https://github.com/perl-catalyst/FCGI/issues/13. The cause might be that the socket is being created somewhere below ${worksrcpath} and so its path name is much too long than allowed.

[ballapete (Peter "Pete" Dyballa)]

Another case with p5.34-dbd-pg:

--->  Computing dependencies for p5.34-dbd-pg.
--->  Testing p5.34-dbd-pg
Executing:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5-dbd-pg/p5.34-dbd-pg/work/DBD-Pg-3.18.0" && /usr/bin/make test 
"/opt/local/bin/perl5.34" -MExtUtils::Command::MM -e 'cp_nonempty' -- Pg.bs blib/arch/auto/DBD/Pg/Pg.bs 644
PGINITDB="/opt/local/lib/postgresql16/bin/initdb" PERL_DL_NONLAZY=1 "/opt/local/bin/perl5.34" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/00_signature.t ....... skipped: Set the environment variable TEST_SIGNATURE to enable this test
t/00basic.t ............ ok
Please wait, creating new database (version 16.4) for testing
pg_ctl: could not start server
Examine the log output.
# 
# DBI                         Version 1.645
# DBD::Pg                     Version 3.18.0
# Perl                        Version 5.34.3
# OS                          darwin
# PostgreSQL (compiled)       ?
# PostgreSQL (target)         ?
# PostgreSQL (reported)       ?
# Default port                ?
# DBI_DSN                     ?
# DBI_USER                    <not set>
# Test schema                 dbd_pg_testschema
# LANG                        C
# Adjusted:                   initdb
# Error was: Unix-domain socket path "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_perl_p5-dbd-pg/p5.34-dbd-pg/work/DBD-Pg-3.18.0/dbdpg_test_database/data/socket/.s.PGSQL.5440" is too long (maximum 103 bytes) at t/dbdpg_test_setup.pl line 608.
Bailout called.  Further testing stopped:  Cannot continue: connection failed
t/01connect.t .......... skipped: Connection to database failed, cannot continue testing

Test run interrupted!

Test Summary Report
-------------------
t/01connect.t        (Wstat: 65280 (exited 255) Tests: 0 Failed: 0)