New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bleadperl v5.25.2-28-g8bf4c40 breaks METADOO/Tie-REHash-1.05.tar.gz #15410
Comments
From @andkbisect commit 8bf4c40 Change scalar(%hash) to be the same as 0+keys(%hash) diagnostics http://www.cpantesters.org/cpan/report/6948c51c-39fa-11e6-8ca3-5344607dd3ab perl -V Summary of my perl5 (revision 5 version 25 subversion 3) configuration: Characteristics of this binary (from libperl): |
From @demerphqOn 25 June 2016 at 13:02, Andreas J. Koenig via RT
This tests that scalar() passes through to the perl internal like($pre_v5_8_3 ? tied(%hash)->scalar : scalar(%hash), qr{\d+/\d+}, It could be changed to only test the booleanness of the scalar(%hash), Yves |
The RT System itself - Status changed from 'new' to 'open' |
From @eserteOn Sun Jun 26 09:52:37 2016, demerphq wrote:
Another victim: |
From @andkalso affected Ticket: garu/Data-Printer#98 -- |
From @eserteAlso affected: SKIM/Tie-Hash-Check-0.03.tar.gz |
From @jkeenanOn Wed, 24 Aug 2016 18:25:06 GMT, slaven@rezic.de wrote:
This BBC failure has been reported Resolved: https://rt.cpan.org/Ticket/Display.html?id=117194 |
From @jkeenanOn Sun, 21 Aug 2016 16:49:28 GMT, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:
This BBC failure has been reported resolved at github level, awaiting CPAN release: -- |
From @jkeenanIn Tie-REHash's bug tracker (https://rt.cpan.org/Ticket/Display.html?id=115659#txn-1693542) I have presented the maintainer with Yves's options for fixing the failing test or with the option of simply deleting it. We've communicated with all of the CPAN distros mentioned in this ticket. So I'm resolving the ticket. Thank you very much. -- |
@jkeenan - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#128482 (status was 'resolved')
Searchable as RT128482$
The text was updated successfully, but these errors were encountered: