Today mischief befalls me. CPAN::Reporter::Smoker 0.05 goes nuts, sends 
out who knows how many bogus FAILs and after I come home from work I 
find sitting in my inbox several module authors' replies to point that 
out. One suggested to shut it down, and so I did. Three dutifully 
obliged to cc the cpan-testers list as it said in the report, so none 
of the replies landed here, but that is a topic for another mail.

My smoker ballooned the -I includes to enormous sizes of up to 1500 
additional directories and during testing programs could not be 
executed anymore. I pasted an excerpt at <http://sial.org/pbot/30510> 
and truncated the long lines from 569250 characters to 300.

I would have finished with my investigation earlier, if not for two 
reasons.
➀ I am not able to keep copies of the mails the smoker sends out. The 
system is simple, but unflexible like that and I am not the mail admin 
of that machine, so I cannot do magic behind the scenes to make it 
work. Tips welcome.
➁ The reports do not show up in the public web archives. I assume this 
is due to <http://xrl.us/bhitc>, but the situation is not so simple 
anymore. Long ago I already sent a miniscule amount of reports using a 
different setup, and I was also subscribed to cpan-testers to make the 
reports go right through, and they did. I was subscribed until 
2007-09-23, when the mails just stopped coming. I thought it must be 
because of the switch-over to -discuss, and we had -discuss already for 
a month and at that time, I was reading testers for the chatter only 
anyway, so I shrugged and did not care to think about that strange 
event anymore.

According to ~/.cpanreporter/reports-sent.db I sent 2624 reports in the 
last ten days. I guess they are held now for inspection somewhere, and 
I cannot subscribe to cpan-testers to make reports go right through 
because the list does not allow that anymore since recently. So would 
the responsible inspection person please tell me what I need to do?

PS: Next time I will think harder about a good mail subject.

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to