Closed karenetheridge closed 8 years ago
It would be useful if you link to the report directly.
Is Log::Log4perl up to date? If not, does updating it solve the issue?
It would be useful if you link to the report directly.
I can't; it was just generated :)
Everything is up to date; this is a brand new 5.23.6 install (which was just released today).
Are you saying it is specific to 5.23.6?
This can be reproduced with parallel testing (i.e. using HARNESS_OPTIONS=j4 or so). log4perl.t and log4perl-category.t probably share the same hardcoded temporary file. See also http://www.cpantesters.org/cpan/report/5914459a-a4c7-11e5-b0d8-f74caa3802c5 for another test report.
Thanks for the report! Now waiting for a patch to come in :)
as in the cpantesters report that has been submitted under my name: