[SOLVED] Why do some modules not get tested

[sanbeg]

I've recently started uploading modules to CPAN. Usually, one I upload a module it starts running tests fairly quickly, and I'd start seeing reports after an hour or so.

I updated two modules about two weeks ago, and so far I haven't seen a test report on either of those. These were fairly minor updates; earlier versions had regular test reports.

• http://search.cpan.org/~sanbeg/Directory-Iterator-PP-1.000001/
• http://search.cpan.org/~sanbeg/Directory-Iterator-XS-1.000002/

[tobyink]

The CPAN testers website is having problems at the moment. Normal service is expected to resume in a couple of weeks.

http://blog.cpantesters.org/diary/152

Slaven Rezic and Andreas Koenig have set up an interim service. Here are the results for those two distributions:

• http://217.199.168.174/cgi-bin/cpantestersmatrix.pl?dist=Directory-Iterator-PP
• http://217.199.168.174/cgi-bin/cpantestersmatrix.pl?dist=Directory-Iterator-XS

[bulk88]

As tobyink said, there are big problems with the cpantesters website right now. Also see http://www.nntp.perl.org/group/perl.cpan.testers.discuss/. I am waiting for reports myself.

[mje]

The above answers are probably what you are looking for but I just thought I'd let you know of a few more.

Some modules don't receive smoke reports from automated smokers because they are black listed. I'm not smoking right now but I had a list of black listed modules for various reasons - tests took way too long, downloaded loads of stuff, prompted without using prompt etc

Some automated testers abort a test if it takes longer than some time - assuming the test has hung.