BeneSphinx has asked for the wisdom of the Perl Monks concerning the following question:

Dear Monks, I am attempting to install a Perl-based webserver named Starman on my computer (Strawberry Perl, 64-bit). However something is happening which causes it to hang on a test. I have attempted force install in CPAN, but it still runs the tests. I'm guessing force install just causes it to ignore the results of the tests, but that doesn't help me since the hanging test prevents the install from proceeding. What I really need is some sort of "ultra force" that prevents the tests from even running. Is there anything like that? What else should I do? Thank you.
  • Comment on totally skipping a test in CPAN ("ultra force!")

Replies are listed 'Best First'.
Re: totally skipping a test in CPAN ("ultra force!")
by Athanasius (Archbishop) on Sep 21, 2017 at 03:04 UTC

    Hello BeneSphinx,

    To install without tests, you can use the -T option with cpan, or the -n option with cpanm.

    But the “DESCRIPTION” section of the Starman documentation states:

    Starman is a PSGI perl web server that has unique features such as:
    ...
    UNIX only

        This server does not support Win32.

    — so, even if you can get it to install, it’s not likely to work for you on Windows. :-(

    Hope that helps,

    Athanasius <°(((><contra mundum Iustus alius egestas vitae, eros Piratica,

      Thank you Athanasius for the info!! Sorry that I missed that in the docs. I need to learn to check for Windows compatibility. Well, I guess it's good to know for sure.

        I need to learn to check for Windows compatibility.

        You did, but you decided to ignore the results and try to skip the tests instead. Why!?

        A reply falls below the community's threshold of quality. You may see it by logging in.
Re: totally skipping a test in CPAN ("ultra force!")
by Anonymous Monk on Sep 22, 2017 at 14:18 UTC
    Some tests used by such software attempt to perform network connections but those attempts should eventually time-out. You should wait for them to do so. If you seem to have encountered a test that does not, you should open a bug-report against the package which details the circumstances of the problem. (In any case, the package developer can add a note to the effect that "such-and-such test might take so-many seconds.")