On Sun, Jun 15, 2008 at 3:59 PM, Michael Peters <[EMAIL PROTECTED]> wrote: > I had mentioned this to some people at the Oslo QA Hackthon, but I've been > really busy since then. Now that I'm at YAPC, I should have some good hacking > time, so here goes... > > My place of business (Plus Three, LP) has allowed me to host the smolder > install > on our smolder server and I've setup Parrot as a project there: > http://smolder.plusthree.com/app/public_projects/details/8 > > I've done a checkout from svn and ran the tests and produced a TAP archive > (more > on that later) and uploaded it as the first report: > http://smolder.plusthree.com/app/public_projects/smoke_reports/8 > http://smolder.plusthree.com/app/public_projects/report_details/1192 > > And an Atom feeds here: > http://smolder.plusthree.com/app/public_projects/feed/8 (all) > http://smolder.plusthree.com/app/public_projects/feed/8/failed (failed) > > So I need to do a couple of things to get these kinds of reports in an > automated > way. > > 1) Update the test harness to use Test::Harness 3. > I'm assuming that right now parrot just uses what ever is installed with the > Perl that's on that machine right? Would it be ok to bundle the new T::H with > Parrot?
In general, we're trying to avoid including more non-core modules with parrot. However I personally wouldn't have a problem with this bundle until we resolve the issues with Bundle::Parrot. (issues == we don't actually require it. =-) > 2) Change t/harness to allow an --archive flag which tells it to create a TAP > Archive (which is basically just a tar file with a bunch of TAP files in it). Sure. > There is TAP::Harness::Archive which does this (and it's what prove -a uses > behind the scenes), but I don't know if it's appropriate to bundle this with > Parrot since it has a dependency on YAML::Tiny and Archive::Tar (which has *a > lot* of other dependencies - > http://cpandeps.cantrell.org.uk/?module=Archive%3A%3ATar&perl=any+version&os=any+OS). > > The act of creating a TAP archive is pretty simple with T::H3 if we have a > tar > utility (and also preferrably gzip). So should I just do that directly in > t/harness (or Parrot::Test::Harness) If we only need this for smolder (and not vanilla "make test"), then I would say don't bundle this, but die nice if it's not installed. And we'll get them added to Bundle::Parrot. > 3) Change the buildbot setup you already have to run the tests and then submit > the TAP archives to the Smolder server. This should be pretty simple once I've > gotten the changes to t/harness. > > Questions? Comments? Verbal abuse? > > > -- > Michael Peters > Plus Three, LP > > -- Will "Coke" Coleda
