On Wed, Oct 01, 2008 at 11:09:59AM -0400, David Golden wrote:
> On Wed, Oct 1, 2008 at 8:43 AM, Barbie <[EMAIL PROTECTED]> wrote:
> > There has been a recent incident where an author had deleted a
> > distribution from CPAN, but is still receiving test reports for them
> > (via the Daily Report).
> >
> > I'm assuming that that tester in question is using a CPAN-Mini mirror or
> > similar to retrieve the modules for testing. If this is the case for
> 
> Not necessarily.

Agreed, and I understand the delay of PAUSE too. But the distribution is
not on CPAN :) However, CPAN-Mini repos are sync'ed up manually rather
than the automated mirror updates ... usually. I just wanted to ensure
that anyone using CPAN-Mini repo ensures they do a refresh before
testing, or at least daily if they are testing continuously.

> Ideally, CPAN Testers should use a frequently updating mirror to avoid
> testing modules recently deleted from the master CPAN.  But that can't
> be uniformly guaranteed.  And nothing prevents testers from testing
> module that were recently uploaded and then immediately scheduled for
> deletion in the 72 hour delay window.

Agreed and in those cases it's just tough luck if you get several
reports for that distribution/version.

> Did the author get a report from a test run during the scheduled
> deletion period or after it?

>From the email I've had, the implication is that this
distribution/version was deleted a few weeks ago, although I cannot
guarantee that at the moment. I'm waiting for him to confirm it.

> A better approach is probably to filter out or flag (for later
> exclusion) any reports in the database for distributions no longer
> available on CPAN.

This will be the case when I get a chance to amend the notification
system code, but in the meantime it just seemed a good idea to suggest
that anyone using a CPAN-Mini repo in their test environment, to refresh
regularly.

Cheers,
Barbie.
-- 
Birmingham Perl Mongers <http://birmingham.pm.org>
Memoirs Of A Roadie <http://barbie.missbarbell.co.uk>


Reply via email to