Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

chromatic (983)

chromatic
  (email not shown publicly)
http://wgz.org/chromatic/

Blog Information [technorati.com] Profile for chr0matic [technorati.com]

Journal of chromatic (983)

Friday January 02, 2009
02:39 AM

A Little Parrot Task for the Interested

[ #38201 ]

If you have some spare time in the next couple of weeks, the Parrot TODO/skip test review is an embarrassingly parallel milestone which is suitable for anyone who can read code written in Perl 5 and skim code written in PIR.

All you need to do is pick a test file not listed on that page which contains either TODO or SKIP (capitalization does not matter) and list it on the page, with a count of the affected tests and a marker whether there's an RT or TT referenced in the reason.

That's it.

You can mail the Parrot developer list directly or tell someone in #parrot on irc.perl.org.

Reviewing one test file is a help. Reviewing more is wonderful. If you have five minutes, you can do it!

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • When you say 'RT', I assume you mean a ticket in the parrot track of rt.perl.org [perl.org]? And what's 'TT'? I've no idea. And these are only parrot tests we're talking about, nothing in any of the languages/*/t directories, right?

    And why does one need to be able to skip PIR? I've seen RT numbers in PIR, so I assume that's why you need to be able to skim it, but I wasn't sure. And maybe a short explanation for folks on how to match up a given test file with its associated PIR might help. Is it just a simple mat

    • When you say 'RT', I assume you mean a ticket in the parrot track of rt.perl.org?

      Yes.

      And what's 'TT'?

      We've migrated to Parrot Trac [parrot.org] for all new tickets. New reports should go there. I know it's a little confusing.

      And these are only parrot tests we're talking about, nothing in any of the languages/*/t directories, right?

      Right.

      And why does one need to be able to [skim] PIR?

      You need to know enough to identify when we skip or TODO a test in PIR. That's all.

      And maybe a short explanation for folks on h