Re: Let's try for a better CPAN experience

If you are setting the testing environment variables to your requirements then many of these problems should be eliminated. If a test suite doesn't honour the variables then that's worth raising as an issue against the dist in question.

Don't run extensive "timeout" tests unless you absolutely have to.

If you are referring to idle timeouts then installing/updating your modules in parallel can mitigate that. However, I agree with you and long timeouts should not be part of a standard test suite at all.

🦛

Comment on Re: Let's try for a better CPAN experience

Replies are listed 'Best First'.
Re^2: Let's try for a better CPAN experience by cavac (Prior) on Jun 01, 2021 at 13:50 UTC
Yes, you can work around some of that stuff by environment variables. My thinking was more along the lines of a standard setup. Also, it would be great to have an option in the cpan shell config to just set those whenever calling the shell for installing a dist. At least, i haven't seen an option like this. `perl -e 'use Crypt::Digest::SHA256 qw[sha256_hex]; print substr(sha256_hex("the Answer To Life, The Universe And Everything"), 6, 2), "\n";'`	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Let's try for a better CPAN experience
by cavac (Prior) on Jun 01, 2021 at 13:50 UTC

Yes, you can work around some of that stuff by environment variables. My thinking was more along the lines of a standard setup.

Also, it would be great to have an option in the cpan shell config to just set those whenever calling the shell for installing a dist. At least, i haven't seen an option like this.

perl -e 'use Crypt::Digest::SHA256 qw[sha256_hex]; print substr(sha256_hex("the Answer To Life, The Universe And Everything"), 6, 2), "\n";'

[reply]
[d/l]