| Subject: | System perl used in tests |
See http://matrix.cpantesters.org/?dist=Plack-Middleware-Profiler-NYTProf+0.17 for an overview of test reports --- there are quite a lot fail reports visible here.
I think that the problem here is that many custom perls run without changing $PATH, so tools like "nytprofhtml" etc. are not visible, and calling "perl" is not the correct one (usually /usr/bin/perl). In most cases it helps if either $^X is used somewhere, or $ENV{PATH} is extended by $Config{scriptdir}, or when calling own scripts then call the blib/script version where the shebang is usually corrected (unless the shebang was originally something like #!/usr/bin/env perl; in this case correct shebang replacement does not happen).