We've accumulated a couple of interesting build-time options that might
be the cause of lots of exciting CPAN module failures - refcounted
stack, and silent-no-taint.
Do we have any way to start bulk testing of CPAN modules with these
options turned on?
It strikes me that it would be a fun and relatively simple task for the
kinds of folks who like to make CI systems, to build some kind of
differential test mechanism that can take a CPAN module, try testing it
against two different perls - one with the interesting build option,
one without - and look for differences in output. I.e. if it fails with
refcounted stack or silent-no-taint, but passes without, that would be
an interesting thing to report.
Is this the sort of thing someone wants to look into?
--
Paul "LeoNerd" Evans
leonerd@leonerd.org.uk | https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/
be the cause of lots of exciting CPAN module failures - refcounted
stack, and silent-no-taint.
Do we have any way to start bulk testing of CPAN modules with these
options turned on?
It strikes me that it would be a fun and relatively simple task for the
kinds of folks who like to make CI systems, to build some kind of
differential test mechanism that can take a CPAN module, try testing it
against two different perls - one with the interesting build option,
one without - and look for differences in output. I.e. if it fails with
refcounted stack or silent-no-taint, but passes without, that would be
an interesting thing to report.
Is this the sort of thing someone wants to look into?
--
Paul "LeoNerd" Evans
leonerd@leonerd.org.uk | https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/