Skip Menu |

This queue is for tickets about the SQL-QueryBuilder-Pretty CPAN distribution.

Report information
The Basics
Id: 115158
Status: open
Priority: 0/
Queue: SQL-QueryBuilder-Pretty

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

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



Subject: pod test fails (encoding problem)
The t/pod.t test fails like this: ... # Failed test 'POD test for blib/lib/SQL/QueryBuilder/Pretty.pm' # at /opt/perl-5.18.2/lib/site_perl/5.18.2/Test/Pod.pm line 187. # blib/lib/SQL/QueryBuilder/Pretty.pm (222): Non-ASCII character seen before =encoding in 'André'. Assuming UTF-8 ... It seems that adding "=encoding utf-8" directives on top of the pods would fix the problem.
On 2016-06-07 22:14:49, SREZIC wrote: Show quoted text
> The t/pod.t test fails like this: > > ... > # Failed test 'POD test for blib/lib/SQL/QueryBuilder/Pretty.pm' > # at /opt/perl-5.18.2/lib/site_perl/5.18.2/Test/Pod.pm line 187. > # blib/lib/SQL/QueryBuilder/Pretty.pm (222): Non-ASCII character seen > before =encoding in 'André'. Assuming UTF-8 > ... > > It seems that adding "=encoding utf-8" directives on top of the pods > would fix the problem.
While this test failure is indeed an issue that should be corrected, please don't allow pod, critic or kwalitee tests to run for normal user installs, as they make the installation fail unnecessarily when newer versions of the tester module introduces errors that you cannot anticipate. Also spelling tests are dependent on what dictionaries are installed locally, and critic tests use all plugins that are installed, both of which cannot be predicted in advance. Either move them to xt/, or guard them with: plan skip_all => "These tests are for authors only!" unless $ENV{AUTHOR_TESTING} or $ENV{RELEASE_TESTING};