Skip Menu |

This queue is for tickets about the Test-PDL CPAN distribution.

Report information
The Basics
Id: 105457
Status: resolved
Priority: 0/
Queue: Test-PDL

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

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



Subject: Tests fail with Test::Deep 0.116
The deep.t test may fail with a "Can't call method "cmp_deeply" on unblessed reference" message. See http://www.cpantesters.org/cpan/report/2701e6a4-19e7-11e5-9ea2-35c8e0bfc7aa for a sample fail report. analysis.cpantesters.org thinks that the failures happen only with Test::Deep 0.116, see http://analysis.cpantesters.org/solved?distv=Test-PDL-0.12 Maybe it's best to make sure that another version than 0.116 is installed, e.g. by writing something like the following in Makefile.PL (untested): if (eval { require Test::Deep; $Test::Deep::VERSION == 0.116 }) { $test_deep_prereq_version = 0.117; } else { $test_deep_prereq_version = 0; # or whatever the minimum version is } ... PREREQ_PM => { ..., 'Test::Deep' => $test_deep_prereq_version, ... } or just increase the Test::Deep minimum version to 0.117 for all.
On 2015-06-23 22:27:13, SREZIC wrote: Show quoted text
> The deep.t test may fail with a "Can't call method "cmp_deeply" on > unblessed reference" message. See > http://www.cpantesters.org/cpan/report/2701e6a4-19e7-11e5-9ea2- > 35c8e0bfc7aa for a sample fail report. analysis.cpantesters.org thinks > that the failures happen only with Test::Deep 0.116, see > http://analysis.cpantesters.org/solved?distv=Test-PDL-0.12
Test::Deep 0.116 is broken; everything that uses Test::Deep would fail its tests. However, it was only the latest version for less than a day, so I'm not sure it's worth putting in a dynamic prereq check for that. Huge amounts of the cpan would have to do a re-release. I've decided not to do it for my distributions.
I would suggest this ticket can safely be closed.
On 2019-02-28 11:49:14, ETJ wrote: Show quoted text
> I would suggest this ticket can safely be closed.
Closing: a new release is there and the old problem is not visible in the matrix anymore (but it seems that there are other problems now...)