Re: Installing LWP::Protocol::https Failure

I love metacpan so much I donate to it monthly. Why? Am I just generous? No. The amount of time pales in comparison to my meager contribution. My favorite feature is on the left hand side -- summary test results and links to the CPAN tester's results. Seriously, for me this is religion -- before I bang my head against the wall on a module I need to see those results. For this module I see red. Twenty eight failures spanning successive Perl releases. No. Skip. Look for alternative.

Celebrate Intellectual Diversity

Comment on Re: Installing LWP::Protocol::https Failure

Replies are listed 'Best First'.
Re^2: Installing LWP::Protocol::https Failure by SankoR (Prior) on Jan 13, 2024 at 20:25 UTC
And I see 1,389 results that pass. And hundreds of other modules that depend on it so it installs just fine for a ton of people. Besides, a DNS error is hardly a problem when the focus of the code isn't name resolution. They could have installed the module without bothering with the test suite so I'm not sure what the goal is. I'd suggest crabbit switch to HTTP::Tiny with SSL support properly installed. Less to bother with because HTTP::Tiny has been a core module for 13 years now.	[reply]
Re^2: Installing LWP::Protocol::https Failure by Bod (Parson) on Jan 14, 2024 at 00:23 UTC
For this module I see red. Twenty eight failures spanning successive Perl releases But have you looked at the test results of the fails or just that they are red? I haven't looked at them all but I checked half a dozen of the fails. Every one I looked at failed in the same place... `# Failed test 'success status' # at t/example.t line 19. # Failed test 'have header Client-SSL-Socket-Class' # at t/example.t line 29. # Failed test 'have header Client-SSL-Cipher' # at t/example.t line 44. # Failed test 'found expected document content' # at t/example.t line 46. # 'Can't connect to www.example.com:443 (Name do +es not resolve)` [download] These are all the places that the tests will fail if the host machine cannot retrieve the webpage www.example.com. To me, this would suggest that the problem is not with the module but instead with an incompatibility between the module's needs and the host environment. As LWP::Protocol::https is only useful to fetch HTTPS requests, it seems reasonable that the tests fail when the host cannot retrieve a webpage.	[reply] [d/l]