On 2014-12-28 22:26:08, ETHER wrote:
Show quoted text> On 2014-12-25 19:15:01, ETHER wrote:
> > 11:02 < ether> ingy's Test::LeakTrace error is weird
> > 11:02 < ether>
https://rt.cpan.org/Ticket/Attachment/1446024/768815/
> > 11:12 < autarch> ether: yeah, I can't reproduce it on my machine
> > 12:59 < haarg> i can reproduce it
> > 13:07 < haarg> fails with List::Util 1.34, passes with 1.41
> > 13:12 < haarg> passes with 1.35
> > 14:05 < ether> neat
> > 14:06 < ether> so we can at least bump up the required dep for
> > List::Util
> > 14:06 < ether> were all List::Util before 1.35 similarly affected?
>
>
> I can bump up the dep of List::Util to 1.35, but I'd like to get some
> insight as to what is happening here... particularly if there is some
> bug either in Moose or List::Util that should be addressed.
I was able to reproduce this as well, so I bisected down to this commit fixing things in Scalar-List-Utils:
commit ddc9bdfeba0dc1ec189a2595d921d39be4278b36
Author: Paul "LeoNerd" Evans <leonerd@leonerd.org.uk>
Date: Fri Oct 18 13:03:06 2013 +0100
Neater muxing logic on any/all/none/notall; have them all return PL_sv_{yes,no}