Front page | perl.perl5.porters |
Postings from August 2010
Summary: I have ported my 'smoke-me' script to my Windows 2000 VM, so now you'll receive both Linux x86_64 and MSWin32 (MSVC80FREE) smoke reports when you create a "smoke-me/XXX" branch in the perl5.git.perl.org repository. Why? So you can test out "break the build" changes more thoroughly and on more platforms before integrating them into blead and breaking everybody. How fast? My Win32 VM finishes a smoke in ~4 hours. My Linux machine runs a much more thorough test and finishes in ~18 hours. Note that they will only do one branch at a time so those are best case numbers, unless your branch has build failures in which case it'll go a lot faster. Where? They're organized by comitter name: http://m-l.org/~perl/smoke/perl/win32/smoke-me/ http://m-l.org/~perl/smoke/perl/linux/smoke-me/ Reports are also sent to the smoker report mailing list and directly to the most recent committer on the branch. They are NOT sent to p5p. The 'smoke-me' script doesn't mind if you delete, rebase, and push your branch back under the same name. Make sure to do that in the correct order or the git server will care. Smokes are done in order of which out-of-date branch has the oldest commit as its most recent one. The script also pauses for an hour if it has nothing to do, so that could delay your report up to an hour depending on when it see yours branch. My next step is to lower the bus factor and make it run on more machines than just my two (by perhaps vampiring the Test::Smoke config file). (Note that I'm having some trouble with zombie processes on my Win32 machine which I believe are due to friendly fire incidents from the watchdog when two separate smokes are running simultaneously. I had this problem with io_sock.t before and patched it to use alarm() instead but it could be more widespread. In any event, I'll whack errant zombies if they do show up, but it will delay reports some if I have to.) -- George Greer