All the Perl that's Practical to Extract and Report
use Perl Log In
barbie (2653)
reversethis-{ku. ... m} {ta} {eibrab}
http://barbie.missbarbell.co.uk/
Leader of Birmingham.pm [pm.org] and a CPAN author [cpan.org]. Co-organised YAPC::Europe in 2006 and the 2009 QA Hackathon, responsible for the YAPC Conference Surveys [yapc-surveys.org] and the QA Hackathon [qa-hackathon.org] websites. Also the current caretaker for the CPAN Testers websites and data stores.
If you really want to find out more, buy me a Guinness
Links:
Memoirs of a Roadie [missbarbell.co.uk]
[pm.org]
CPAN Testers Reports [cpantesters.org]
YAPC Conference Surveys [yapc-surveys.org]
QA Hackathon [qa-hackathon.org]
Ahhh! That wasn't DEBUG mode!
To all those authors who received a second copy of their Daily Summary Report this morning, my apologies.
Yesterday I made several changes to the backend code, and this morning I wanted to perform a test run to ensure all the report emails would be generated correctly. Unfortunately the DEBUG setting used in the configuration to normally do this wasn't set (DEBUG disables the report sending). As a consequence it performed a live run instead, repeating the same emails for the original live run. In order to avoid this in future, I've added a better command line switch so I can forcibly run it in DEBUG mode, so it shouldn't happen again.
On a positive note, all the emails did appear to be generated correctly and there was no local errors, so at least the changes worked
--Larry Wall in stab.c from the perl source code
Ahhh! That wasn't DEBUG mode! 0 Comments More | Login | Reply /