Skip Menu |
 

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Metabase CPAN distribution.

Report information
The Basics
Id: 57089
Status: new
Priority: 0/
Queue: Metabase

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

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: Track (and report?) warnings from smoker test runs.
Download (untitled) / with headers
text/plain 1010b
This came up on #cpantesters-discuss and I wanted to put it somewhere for later consideration: Many of the deprecation messages that showed up in 5.12 haven't been fixed in CPAN. The reason is that even though they were present in 5.11, Smoke testers don't look for warning messages. I was thinking if smoke testers reported on deprecation messages (warnings), it would get things fixed faster. It would also be much easer for p5p to deprecate things from core as they would be able to get reporting on how much noise a dev release caused as a regression. I'm not clear on the full scope of the Metabase project, but my end goal would be that the authors be notified when a smoke test fails with maybe a WARN class that shows what warnings the test suite emitted? Because core emits their deprecation messages as warnings, this would also be trapped. If authors have meaningful warnings in their test suite, they can easily filter them out of the test suite run with the use of Test::NoWarnings.


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.