Would you consider machinery to ignore warnings from dependencies #1

ribasushi opened this Issue Feb 27, 2013 · 2 comments


None yet

2 participants

This module has the same pitfall like Test::NoWarnings had - it will get tripped up by a working-but-warning-spewing dependency. Would you consider enhancements to analyze the caller() on every trapped warning and pass-through anything that was not emitted from t/ lib/, etc (similar heuristics to strictures.pm)

ghost commented Feb 27, 2013

With an option to disable that, sure. I could imagine that some people
might want to be brutal and fail even warnings from dependencies.

But the default could be smart.


ghost commented Mar 10, 2013

I've added this in 0.002

@dagolden dagolden closed this Mar 10, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment