07. 08. 2023. u 07:13, Bodo Hugo Barwich piše:

Dear CPAN-Testers,

Test Scenario "*Process-SubProcess-2.1.3 5.18.2 GNU/Linux*" fails when trying to load "/Getopt::Long::Descriptive/" as seen on:
https://www.cpantesters.org/cpan/report/a62cd144-3498-11ee-98b0-b3c3213a625c
"
Can't load '/home/cpan/pit/jail/cm2baDMkN6/lib/perl5/x86_64-linux-thread-multi-ld/auto/Params/Util/Util.so' for module Params::Util: /home/cpan/pit/jail/cm2baDMkN6/lib/perl5/x86_64-linux-thread-multi-ld/auto/Params/Util/Util.so: undefined symbol: Perl_xs_version_bootcheck at /home/cpan/pit/jail/cm2baDMkN6/lib/perl5/x86_64-linux-thread-multi-ld/XSLoader.pm line 96.  at /home/cpan/pit/jail/cm2baDMkN6/lib/perl5/x86_64-linux-thread-multi-ld/Params/Util.pm line 68. Compilation failed in require at /home/cpan/pit/jail/cm2baDMkN6/lib/perl5/Data/OptList.pm line 7. BEGIN failed--compilation aborted at /home/cpan/pit/jail/cm2baDMkN6/lib/perl5/Data/OptList.pm line 7. Compilation failed in require at /home/cpan/pit/jail/cm2baDMkN6/lib/perl5/Sub/Exporter/Util.pm line 6. BEGIN failed--compilation aborted at /home/cpan/pit/jail/cm2baDMkN6/lib/perl5/Sub/Exporter/Util.pm line 6. Compilation failed in require at /home/cpan/pit/jail/cm2baDMkN6/lib/perl5/Getopt/Long/Descriptive.pm line 271. BEGIN failed--compilation aborted at /home/cpan/pit/jail/cm2baDMkN6/lib/perl5/Getopt/Long/Descriptive.pm line 271. Compilation failed in require at /home/cpan/pit/thr-ld/conf/perl-5.18.2/.cpanplus/5.18.2/build/7SrlCQvp6r/Process-SubProcess-2.1.3/t/../bin/run_subprocess.pl line 15. BEGIN failed--compilation aborted at /home/cpan/pit/thr-ld/conf/perl-5.18.2/.cpanplus/5.18.2/build/7SrlCQvp6r/Process-SubProcess-2.1.3/t/../bin/run_subprocess.pl line 15.
"

Which I find strange since I haven't noticed this issue in any of my testing and deployment scenarios:
https://github.com/bodo-hugo-barwich/Process/actions/runs/5773581039/job/15649686759

Please, can I do something to fix this?

Hi Bodo,


this kind of errors usually happen if tests are running with the wrong perl binary. Most likely you use at some point "/usr/bin/perl" or so (through a shebang or because it's the first perl in user's PATH or explicitly), but the build and tests on the failing smoker system are running with a self-compiled perl, possibly even not located in the user's PATH.


Regards, Slaven

Reply via email to