https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8002
--- Comment #2 from Sidney Markowitz <sid...@sidney.com> --- This is more complicated than I thought. First, CPAN testers are not running perlcritic on their own. The failures are in our own t/percritic.t test Second, they are not enabling more policies than we are. The failures occur running our own test with the same settings that we have. The difference is that not all percritic policies are installed when one installs Perl::Critic abd Test::Perl::Critic. I had to run cpanm Perl::Critic::Policy::Bangs::ProhibitBitwiseOperators to get the bitwiseoperator warnings to show up in t/perlcritic.t So to get our test to get the same results as CPAN testing will find, we'll have to install the policy modules that they have on their test machines. The good news is that we can exclude the policies in t/perlcritic.t the same way as the policies we already exclude and we don't have to sweep through all the code right away. -- You are receiving this mail because: You are the assignee for the bug.