Re: [P6C] problems with revision 1.5 of lib/Parrot/Test.pm

2004-04-21 Thread Allison Randal
Dan Sugalski wrote: > > Applied. (Was there anything besides the /tmp change? That's all that > was in the attachment) Calling 'rel2abs' was necessary so Parrot::Test would have the right path to the test file later when it cd's to the main parrot directory and calls './parrot'. That's all it ne

Re: [P6C] problems with revision 1.5 of lib/Parrot/Test.pm

2004-04-21 Thread Dan Sugalski
At 7:02 PM -0500 4/21/04, Allison Randal wrote: Dan wrote: Well... the big problems we were make-related, with some tinder issues. Basically if any test suite died really hard the testing would stop, and only the last test suite run counted for tinder good/bad reporting. At this point, though,

Re: [P6C] problems with revision 1.5 of lib/Parrot/Test.pm

2004-04-21 Thread Allison Randal
Dan wrote: > > Well... the big problems we were make-related, with some tinder > issues. Basically if any test suite died really hard the testing > would stop, and only the last test suite run counted for tinder > good/bad reporting. > > At this point, though, I'm comfortable making it so that

Re: [P6C] problems with revision 1.5 of lib/Parrot/Test.pm

2004-04-21 Thread Dan Sugalski
At 5:55 PM -0500 4/21/04, Allison Randal wrote: So, very quickly: 1. The main goal is to have unified languages tests, that is, make language-tests would get a list of all the test files for all of the languages, and then run only _one_ harness with all those files. This would allow for one ni

Re: [P6C] problems with revision 1.5 of lib/Parrot/Test.pm

2004-04-21 Thread Allison Randal
Jerome wrote: > > I'm sorry, I've been very busy for 2 weeks, and did not have the time to > continue things regarding this topic. :-( > I hope to have some more time this week-end, but I'm not even sure... It happens. :) > So, very quickly: > 1. The main goal is to have unified languages tests

Re: [P6C] problems with revision 1.5 of lib/Parrot/Test.pm

2004-04-21 Thread Dan Sugalski
At 12:23 AM +0200 4/22/04, Leopold Toetsch wrote: Jerome Quelin <[EMAIL PROTECTED]> wrote: 7. The patch has some, erm, "action at distance" problems, such as the pasm files put in /tmp Is that a side effect or needed? It's just a side-effect, and we can put the old behavior back, I expect. --

Re: [P6C] problems with revision 1.5 of lib/Parrot/Test.pm

2004-04-21 Thread Leopold Toetsch
Jerome Quelin <[EMAIL PROTECTED]> wrote: > 7. The patch has some, erm, "action at distance" problems, such as the > pasm files put in /tmp Is that a side effect or needed? leo

Re: [P6C] problems with revision 1.5 of lib/Parrot/Test.pm

2004-04-21 Thread Jerome Quelin
Allison Randal wrote: > Okay, languages/perl6 is failing all its tests. [...] > Will or Jerome, could you take a minute to explain the direction > you're taking Parrot::Test? I'll patch P6C::TestCompiler to match the > new setup, but I want to do an "architecture sanity check" first. I'm sorry, I'

Re: [P6C] problems with revision 1.5 of lib/Parrot/Test.pm

2004-04-21 Thread Leopold Toetsch
Allison Randal <[EMAIL PROTECTED]> wrote: > Will or Jerome, could you take a minute to explain the direction you're > taking Parrot::Test? I'll patch P6C::TestCompiler to match the new > setup, but I want to do an "architecture sanity check" first. I'd rather have the test files back in our tree.

[P6C] problems with revision 1.5 of lib/Parrot/Test.pm

2004-04-21 Thread Allison Randal
Okay, languages/perl6 is failing all its tests. The problem is in a few recent changes to lib/Parrot/Test.pm. The Perl 6 test module in languages/perl6/P6C/TestCompiler.pm inherits from Parrot::Test, but overrides some subs. P6C::TestCompiler's &generate_pbc_for is writing the .pasm files in subdi