Okay, I think I've fixed the code that generates this: It was being run in a DESTROY block, which means that the database connection may have gone away when it's attempted to be run, maybe. Nothing in any log shows an error to that effect, but that's my present guess.
Perl versions are only updated when new reports come in, so I'm going to come up with a utility to regenerate the Perl versions from the processed reports, and/or from the CPAN mirror. For now, we play the waiting game... Doug Bell d...@preaction.me > On Jul 25, 2017, at 3:37 PM, James E Keenan <jkee...@pobox.com> wrote: > > Today, I had occasion to go to this page: > > http://www.cpantesters.org/distro/U/UR.html#UR-0.46 > > I was trying to track down the CPANtesters report implied in this post: > https://rt.perl.org/Ticket/Display.html?id=131571#txn-1477071 > > ... a failure which presumably would have appeared in perl-5.27.0, i.e., very > recently. > > On the left-hand side of the cpantesters.org page there is a drop-down > labelled "Perl Version". The latest Perl version shown in that box is 5.25.6. > > This is so notwithstanding the fact that the main chart on that page does > list reports of this distro having been tested against perl-5.26.0 -- though > no reports against 5.27.*. > > Can this be remedied? > > Thank you very much. > Jim Keenan
signature.asc
Description: Message signed with OpenPGP
