Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
perl.perl6.internals
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion problems with revision 1.5 of lib/Parrot/Test.pm
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Allison Randal  
View profile  
 More options Apr 21 2004, 3:48 am
Newsgroups: perl.perl6.internals
From: a...@shadowed.net (Allison Randal)
Date: Wed, 21 Apr 2004 02:18:22 -0500
Local: Wed, Apr 21 2004 3:18 am
Subject: [P6C] problems with revision 1.5 of lib/Parrot/Test.pm
Print | View thread | Show original | Report this message | Find messages by this author
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 subdirectories of
languages/perl6/t, but Parrot::Test's &generate_functions is trying to
read them from a flattened directory structure in /tmp/*.
(P6C::TestCompiler is passing arguments to Parrot::Test's
&generate_functions that it no longer accepts, and Parrot::Test is
passing arguments to P6C::TestCompiler's &generate_pbc_for that it
ignores.)

So, the tests are failing either because the expected file in /tmp
doesn't exist, or more often because there's already a .pasm file in
/tmp with the expected name that was left behind by the main Parrot test
run (it seems that names like "basic.t" are common).

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.

Thanks,
Allison


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google