Front page | perl.perl5.porters |
Postings from April 2018
On 04/20/2018 12:29 AM, Dave Mitchell wrote: > On Thu, Nov 23, 2017 at 01:46:58PM -0800, Father Chrysostomos via RT wrote: >> On Thu, 23 Nov 2017 13:08:23 -0800, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote: >>> bisect >>> ------ >>> commit 006c1a1dbd541b84351332b0d315508f789f3bd1 (HEAD, >>> refs/bisect/bad) >>> Author: Zefram <zefram@fysh.org> >>> Date: Wed Nov 15 17:41:29 2017 +0000 >>> >>> fix handling of registered warning categories >>> >>> diagnostics >>> ----------- >>> http://www.cpantesters.org/cpan/report/20cd84d6-cb9d-11e7-a079- >>> a334b34ff3ca >>> >>> Assignment of stale reference at t/39_singletons.t line 68. >>> # Tests were run but no plan was declared and done_testing() was not >>> seen. >>> # Looks like your test exited with 255 just after 11. >>> t/39_singletons.t ............... Dubious, test returned 255 (wstat >>> 65280, 0xff00) >>> All 11 subtests passed >> I opened ticket #132468 for the purpose of creating an API that >> DBM::Deep can use, so that it can be fixed permanently. Currently >> DBM::Deep delves inside warnings.pm internals. > Since the API's now been done, and since it seems agreed that it's > DBM::Dep that needs fixing, is it ok to close this ticket, or at least > remove from the 5.28 blockers list? Removing from 5.28 blockers list makes sense.Thread Previous | Thread Next