Andreas J. Koenig wrote:
Barbie, it's quite serious, I believe we must ask Robert to block apocal
from submitting reports. During the last days his smoker has poisoned
many cpantester pages. I'm listing only 12, there may be more:

| name                            | broken reports |               |
|---------------------------------+----------------+---------------|
| MooseX-Traits-0.07              |              5 |               |
| Devel-PartialDump-0.13          |             12 |               |
| MooseX-Singleton-0.22           |             14 |               |
| MooseX-AttributeHelpers-0.23    |             12 |               |
| WWW-FreshMeat-API-0.03          |             14 |               |
| PerlX-QuoteOperator-0.01        |             11 |               |
| Acme-URL-0.01                   |             11 |               |
| MooseX-ABC-0.04                 |             14 |               |
| XML-Atom-0.37                   |              6 | maybe correct |
| Text-SimpleTable-AutoWidth-0.04 |             11 |               |
| Config-GitLike-1.03             |             14 |               |
| Data-Stream-Bulk-0.07           |             12 |               |
| Method-Signatures-Simple-0.05   |             11 |               |
|---------------------------------+----------------+---------------|

And already posted here:
14-Jan  10: Wrong report submitted for Graphics-ColorNames-2.11
14-Jan  11: Wrong report submitted for CPAN-Testers-ParseReport-0.1.11
15-Jan  22: Another broken report submitted for String-RewritePrefix-0.005

On #cpantesters-discuss I hear about him:

15:22:08 < Hinrik> a couple of days ago in #poe I'm afraid he said something to the effect of "I'm going skiing, see you in a couple of weeks"

I think you are the authority here to approach the mailmaster. WDYT?

Hello all,

Sorry it's took me a while to catch up on this list! When I got home from my vacation I quickly saw this issue and simply shutdown the smokers without further investigation. I didn't have time to follow up on it or even post a reply as family issues came up. My dad had surgery on his left shoulder, and I had to make sure he's ok. Thankfully, he's up and about now, ha! Here's a quick rundown of what happened:

1. The smokers were throttled as per the request. However, I didn't anticipate that it would still send LOTS of reports per day! 2. After having the smokers running for a week and more, producing reliable reports I deemed them OK and safe to be left running while I was gone on vacation. 3. I bade farewell and left on my skiing vacation for almost 2 1/2 weeks. During this time I had no access to the smoker box.
   4. Things exploded. :(

I'm trying to figure out the root cause for the problems, but it's hard to dig through the data when all the reports are blacklisted and not showing up anywhere. I don't have a local cached copy of the reports ( maybe I should do from now on! ) and would have to download them manually. My quick hunch is that one of the VMs somehow got corrupted and modules "mysteriously" went missing. Hence the weird dependency chain fuckups present in the reports.

I have extra free time this week, and will dig through the VMs to try and pinpoint the root cause. I doubt it's an outdated toolchain/reporting module because everything was fully updated before I left. It might be Test::Harness because David Golden sent a report on this list, and it could be the culprit. Let me take some time to explain my setup, so you all could help me correct any mistakes if needed.

The box is an AMD quad-core machine running with 8GB ram. The main OS is "Linux blackhole 2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:53:52 UTC 2009 x86_64 GNU/Linux" and I use it as my day-to-day OS. I use VirtualBox 3.0.12 to load the VMs and assign 1 CPU/1GB ram each. The VMs I am running is:

   1. Ubuntu 9.10 server 64bit
   2. OpenSolaris 2009.6 64bit
   3. FreeBSD 7.2-RELEASE 64bit
   4. NetBSD 5.0.1 64bit
5. Ubuntu 9.10 server 64bit ( the master VM that does the rsync of CPAN, runs the httpgateway, sends emails, etc )

Offtopic: I could run more VMs but my CPUs get choked and I can't do any work! This really is an experimental setup, and once I know everything works smoothly I'll get a dedicated box for this. /me waits for magny-cours :)

The way I smoke CPAN is pretty much the same as Chris Williams, after a lot of talking with him. Kudos goes out to him for doing a lot of the legwork and docs! What I do is build each perl version that successfully passes it's testsuite and install it into a sandbox. Current versions: 5.6.1-5.11.2 ( I haven't got around to building 5.11.4 heh ) After the perl is installed, I go ahead and install the basics necessary to bootstrap the test system. This consists of those modules:

* CPANPLUS ( and it's dependencies and various extra modules like ExtUtils::MakeMaker, EU::CBuilder, EU::ParseXS - they were installed to make sure I don't have an old version lying around ) * Test::Reporter ( and LWP so I can submit reports to my centralized HTTPGateway )
   * CPANPLUS::YACSmoke

After the modules are installed on the perls, I configure the system perl so I can run the smoker script. Again, Chris has done an excellent job of making POE::Component::SmokeBox and I just fire it up and let the reports overwhelm you all! :) What this means is I have almost 15 perls configured per VM, and once a new distribution hits PAUSE, I should send out 60 reports for it. Seeing your preliminary statistics verified my assumption that it was one VM that went haywire, or there would be a lot more FAILs for each distribution.

Sorry for the lengthy post, but I wanted you all to know that I'm serious about CPAN smoking and hope to someday become a big contributor. Expect more follow-ups from me as I continue my investigation into why this happened. Hopefully some of the toolchain/reporting modules have been updated to fix this. If not, I'll be real happy to contribute patches to make sure this doesn't happen again. It's a good feeling to be working with such a wonderful group, and I thank you all for being patient with me as I figure out my setup and hammer out all bugs in it.

Here's some information in case you wanted to contact me or look at my setup:

   Email: p...@0ne.us
   PAUSE id: APOCAL
IRC: apocaly...@magnet, apo...@freenode, apo...@oftc, ap0...@quakenet, apo...@undernet, and I hang out in the #cpantesters-discuss channel My code: http://github.com/apocalypse/perl-misc-files ( compile_perl.pl is the perl compiler, smokebox.pl is the actual smoker script )

Again, my deepest apologies to everyone who had to work overtime to resolve this situation.

~Apocalypse

Reply via email to