I haven't smoked all of CPAN lately, but I believe that Steffen Mueller smoked it against bleadperl recently and it took several days but less than a week.
The thing about typical test reporting rates is that it depends on the rate of new uploads, the size of dependency chains (if those have to be built/installed), and the runtime of the test suites. That's different than smoking all of CPAN, where many of the older distribution have smaller dependency trees and smaller test suites (if any tests at all). They're related, certainly, but I suspect smoking all of CPAN will give you a higher reporting rate than you'd experience just smoking recent uploads. David On Thu, Nov 29, 2012 at 8:56 PM, Kirk Kimmel <kimmel.k.program...@gmail.com> wrote: > We already have all kinds of interesting data about CPAN and what it does > but I could not find something. I have been submitting cpan reports for > over a year and I just started wondering how long does it take to test all > modules on CPAN once, not including versions of Perl? > > I have been trying to keep an eye on my newest vm just to see how long > things take. Right now I estimate a normal hour gets 100 reports done but > some hours are much heavier. > > I think having some public facing data about testing times could be useful > to the community and this is the first thing I thought of. > > Kirk -- David Golden <x...@xdg.me> Take back your inbox! → http://www.bunchmail.com/ Twitter/IRC: @xdg
