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!
When you say 'RT', I assume you mean a ticket in the parrot track of rt.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 matter of reading the stack trace?
Re:Questions
chromatic on 2009-01-02T18:36:12
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 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 how to match up a given test file with its associated PIR might help.
You don't even have to run it; I use the command line
vi $( ack -li TODO t/ ), changing the latter directory appropriately, and read the code.
