Andreas J. Koenig wrote, some time around 02/12/2009 10:06:
Today I'm proud to present what I spent most of my time over the last
few weeks on. During the course I wrote over 200 RT tickets and there is
plenty of material for several hundreds more.
At the moment this is just about running regression analysis between the
variables provided by cpantesters. About 2500 critical releases of the
last three years are examined with all due care. The homepage is a huge
table with plenty of links to zoom in.
http://pause.perl.org:3000/ # main table
http://pause.perl.org:3000/about # blurb
It's running on pause with a low priority catalyst server process, so
please be patient and take it as a private showing. I'll have to work
some more to get this application down to use less memory and CPU. But
of course it's much more fun to get it to *do* more.
Your feedback is highly appreciated. In other words, what would *you*
expect from analytics.cpantesters.org?
I think I understand what this is telling me, but there's a lot of
information and it's difficult to pin-point what is important. Looking
at the File-Path distro, with 300+ passes to 3 or so fails, I can see
what appears to influence the likelihood of a fail.
Then again: looking at BSD-Process, which will fail anywhere except on
FreeBSD, I can't see where it highlights the fact that, well hey, this
module tends to fail with surprising regularity on Linux.
I need a summary that tells me more clearly "this modules tends to fail
in these circumstances".
It wouldn't have to be pretty graphics. Just using color, with red is
bad to green is good would be useful.
Later,
David
--
it's an anthem in a vacuum on a hyperstation, day dreaming days in a
daydream nation
