Skip Menu |

This queue is for tickets about the Dist-Zilla-PluginBundle-Author-ETHER CPAN distribution.

Report information
The Basics
Id: 115444
Status: resolved
Priority: 0/
Queue: Dist-Zilla-PluginBundle-Author-ETHER

People
Owner: ether [...] cpan.org
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.116
Fixed in: 0.117



Subject: Tests fail (with Dist::Zilla::Plugin::Test::CPAN::Changes 0.011?)
See http://analysis.cpantesters.org/solved?distv=Dist-Zilla-PluginBundle-Author-ETHER-0.116#mod%3ADist%3A%3AZilla%3A%3APlugin%3A%3ATest%3A%3ACPAN%3A%3AChanges Test output looks like this: ... # Failed test 'build proceeds normally' # at t/01-pluginbundle-basic.t line 66. # got: 'Can't locate object method "Changes" via package "Dist::Zilla::Plugin::Test::CPAN::Changes" at /opt/perl-5.20.1/lib/site_perl/5.20.1/Dist/Zilla/Plugin/Test/CPAN/Changes.pm line 26. # ' # expected: undef Can't locate object method "Changes" via package "Dist::Zilla::Plugin::Test::CPAN::Changes" at /opt/perl-5.20.1/lib/site_perl/5.20.1/Dist/Zilla/Plugin/Test/CPAN/Changes.pm line 26. # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 255 just after 3. t/01-pluginbundle-basic.t ............. Dubious, test returned 255 (wstat 65280, 0xff00) Failed 1/3 subtests ...
On 2016-06-19 01:05:56, SREZIC wrote: Show quoted text
> See http://analysis.cpantesters.org/solved?distv=Dist-Zilla- > PluginBundle-Author-ETHER- > 0.116#mod%3ADist%3A%3AZilla%3A%3APlugin%3A%3ATest%3A%3ACPAN%3A%3AChanges > > Test output looks like this: > ... > # Failed test 'build proceeds normally' > # at t/01-pluginbundle-basic.t line 66. > # got: 'Can't locate object method "Changes" via package > "Dist::Zilla::Plugin::Test::CPAN::Changes" at /opt/perl- > 5.20.1/lib/site_perl/5.20.1/Dist/Zilla/Plugin/Test/CPAN/Changes.pm > line 26.
This is because Dist::Zilla::Plugin::Test::CPAN::Changes 0.011 contained a bad and untested change (and it was my fault!) -- 0.012 is now indexed, which fixes the problem. A new version of my bundle will be released to bump the prereq requirement.