Skip Menu |

This queue is for tickets about the WWW-YouTube-Info CPAN distribution.

Report information
The Basics
Id: 130363
Status: open
Priority: 0/
Queue: WWW-YouTube-Info

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.06
Fixed in: (no value)



Subject: t/03_get_info.t may fail (https issue?)
On some of my smoker systems the test suite fails: ... no get at https://youtube.com/get_video_info?video_id=_YUugB4IUl4 - at t/03_get_info.t line 11. # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 255 just after 2. t/03_get_info.t .. Dubious, test returned 255 (wstat 65280, 0xff00) All 2 subtests passed ... My guess is that the test fails if LWP::Protocol::https or another https-enabling module is missing --- if this is correct, then it has to be declared as a prereq.
Thanks for reporting this issue! LWP::Protocol::https is declared as a prereq; see: https://metacpan.org/source/EAST/WWW-YouTube-Info-0.06/Makefile.PL Please feel free to reopen this ticket, if the issue persists.
On 2019-08-23 16:50:10, EAST wrote: Show quoted text
> Thanks for reporting this issue! > > LWP::Protocol::https is declared as a prereq; see: > https://metacpan.org/source/EAST/WWW-YouTube-Info-0.06/Makefile.PL > > Please feel free to reopen this ticket, if the issue persists.
OK, then it's something different. I run the failing test with more debugging: $ env PERL5OPT=-MLWP::ConsoleLogger::Everywhere perl -Mblib t/03_get_info.t and the interesting parts of the output are: ==> 429 unknown .-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------. | Text | +-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Sorry...GoogleSorry...We're sorry...... but your computer or network may be sending automated queries. To protect our users, we can't process your request right now.See Google Help for more information.Google Home | '-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------' So it would be good if such a response comes then the test should try to skip it without a failure. And output a little bit of diagnostics for the user.
Good point, I'll look into it. -> reopend