On Sun, Aug 29, 2010 at 09:40:40PM -0400, David Golden wrote: > On Sun, Aug 29, 2010 at 6:56 PM, Tim Bunce <tim.bu...@pobox.com> wrote: > > DBI 1.613_71 was uploaded on the 16th yet for MSWin32 there is only 1 test > > report: > > http://matrix.cpantesters.org/?dist=DBI%201.613_71;reports=1;os=MSWin32 > > > > Any reason for that? (Holiday season?) > > > > Any way it could be improved? > > My guesses: > > I think there are relatively few automated Win32 smokers. From my > personal experience running one in the past, they are slow and prone > to blowing up in weird ways when distributions assume every system has > unix capabilities. > > (Did you know that force killing a process on Win32 can -- in a small > number of cases -- wedge the DLL so that the process can't be > restarted without a reboot?)
No, I didn't. But I'm not surprised. [Sigh.] > I suspect that some the Win32 test reports could have come from > individual testers and they may not upgrade their DBI very often. > > If you want a virtual Win32 machine to do your own tests on, Alias > supposedly can grant CPAN authors access to a Win32 VM cluster from > Microsoft. (I've not personally taken advantage of it.) Interesting. So now I'm thinking I might post a request to dbi-announce and dbi-users for volunteers to run automated DBI/DBD testing on those VMs. Hopefully that'll bring in a few new testers on other platforms as well. To see what was involved for myself I followed the link trail from http://cpantesters.org/ "Become a tester" to http://wiki.cpantesters.org/ "How do I become a tester?" to http://wiki.cpantesters.org/wiki/QuickStart "In the meantime, see Getting Started." to http://wiki.cpantesters.org/wiki/GettingStarted "Quick HowTo for CT 2.0 (under development)" to http://wiki.cpantesters.org/wiki/QuickHowToCT20. Phew! That trail could be shorter. That page says: "If you plan to do automated smoke testing, these steps will ensure that you can send reports to the new CPAN Testers 2.0 server and you will need to look at other articles on this wiki for information on configuring automated testing" But it doesn't give any links for the "other articles on this wiki"! Where it says "Choose between CPAN-Reporter or CPANPLUS for your tools. If you are a first-time tester or don't plan to run an automated smoke testing machine, start with CPAN::Reporter", there seems to be an implied "but if you do plan to run an automated smoke testing machine, then we recommend you start with CPANPLUS::YACSmoke". If so, please make it explicit. There are, later on, links to search.cpan.org for CPAN-Reporter-Smoker and CPANPLUS-YACSmoke, but neither of the links work. this: http://search.cpan.org/dists/CPANPLUS::YACSmoke should be: http://search.cpan.org/dist/CPANPLUS-YACSmoke/ and this: http://search.cpan.org/dists/CPAN-Reporter-Smoker should be: http://search.cpan.org/dist/CPAN-Reporter-Smoker/ At the bottom of the page I suggest adding a heading like "Automated Testing" and move the "If you plan to automate your testing, you will want to investigate ..." paragrapphs here. Uh. Having written the above it dawned on me that it's a wiki, so I created an account and edited the page myself. I added a TODO note for the missing "other articles on this wiki" links as I don't know what to link to. On Mon, Aug 30, 2010 at 07:27:02AM +0200, Burak Gürsoy wrote: > > True, I don't have a smoker setup for example. But every module I test > generates a report (Vista 32bit + ActivePerl 5.12.1 + gcc 3.4.5 at the > moment). > So, you can guess that I rarely test dev versions (I just did for > TIMB/DBI-1.613_71.tar.gz) Thanks! Tim.
