Skip Menu |
 

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Paludis-ResumeState-Serialization CPAN distribution.

Report information
The Basics
Id: 90180
Status: resolved
Priority: 0/
Queue: Paludis-ResumeState-Serialization

People
Owner: Nobody in particular
Requestors: ANDK [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.01000409
Fixed in: 0.01000410



Subject: Fails since v5.17.0-360-g9da1dd8
Download (untitled) / with headers
text/plain 386b
As per subject. Link to the commit: http://perl5.git.perl.org/perl.git/commit/9da1dd8f41c98df713957a658aa8fefcdf57163c Sample fail report: http://www.cpantesters.org/cpan/report/99e4da96-490f-11e3-b447-c0721e63232d This report is with a recent bleadperl and Regexp::Grammars seems to work OK except for the noise it produces. So maybe there's an open issue somewhere. HTH && Thanks,

Thanks.

It was indeed mostly just failing due to Regexp::Grammars, mostly, because the code relied upon a mechanic, the specific mechanic that Regexp::Grammars warning is about, namely: The code was using functions in the same logical scope, but the change in 5.18 meant those functions were no longer visible in the same scope as the text of the regexp they were compiled with.
 

However, it was something that could be coded around, and by simply fully qualifying them the problem vanished.

It was then I discovered the only real bug in my code, in that one of the tests had an implict dependency on the return order of some keys(), which caused a failure.

All of the above should now be fixed, and on their way to a CPAN near you =)



This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.