# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #41674]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41674 >
'language/PIR' tests should show up in unified languages testin
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #41675]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41675 >
Currently 'perl6' is not in unified languages testing.
This i
?id=40455 >
Hi,
since a while 'languages/dotnet' showed up as all red in unified
languages testing, which is
invoked with "make languages-test". The culprits were the usual
bunch:
@INC and pathes to executables.
I have expanded the library search path in the test scripts
Hi,
Thanks to @all working on getting dotnet translator back into unified
language testing. I'll be hacking on the translator more when I return
from consulting work in Spain, so this is certainly good to have. :-)
François PERRAD wrote:
Any other suggestions?
1) remove the need of the fi
s/dotnet' showed up as all red in unified
languages testing, which is
invoked with "make languages-test". The culprits were the usual bunch:
@INC and pathes to executables.
I have expanded the library search path in the test scripts. Also
DotnetTesting.pm now asks
Parrot::Test for
s/dotnet' showed up as all red in unified
languages testing, which is
invoked with "make languages-test". The culprits were the usual bunch:
@INC and pathes to executables.
I have expanded the library search path in the test scripts. Also
DotnetTesting.pm now asks
Parrot::Test for
ed in unified
languages testing, which is
invoked with "make languages-test". The culprits were the usual bunch:
@INC and pathes to executables.
I have expanded the library search path in the test scripts. Also
DotnetTesting.pm now asks
Parrot::Test for the path to the parrot executable.
C
Bernhard Schmalhofer (via RT) wrote:
following the lead of TCL, I have adapted the Parrot m4 test scripts
to the new unified testing scheme.
Applied, thanks
leo
At 6:33 PM +0200 4/8/04, Jerome Quelin wrote:
Will Coleda wrote:
Update to this patch -
Jerome has identified an issue with the language testing patch -
[...]
The following bits of the Parrot::Test patch need to be reversed,
which then keeps the perl6 test suite happy, and should remove the
la
Will Coleda wrote:
> Update to this patch -
> Jerome has identified an issue with the language testing patch -
[...]
> The following bits of the Parrot::Test patch need to be reversed,
> which then keeps the perl6 test suite happy, and should remove the
> last /showstopper/ to applying the patch.
Update to this patch -
Jerome has identified an issue with the language testing patch - turns
out that perl6's test suite has carnal knowledge about Parrot::Test.
One of the changes I made to Parrot::Test broke the perl6 test suite.
The following bits of the Parrot::Test patch need to be revers
On Sun, Mar 28, 2004 at 02:11:01AM -0500, Will Coleda wrote:
> use lib qw(../lib ../../lib ../../../lib);
> use Parrot::Config;
> my $path = $INC{"Parrot/Config.pm"};
> $path =~ s:lib/Parrot/Config.pm$::;
>
> to figure out the path to the parrot executable.
>
> Is this too evil, or should I go a
Hurm. this didn't make it to the list - Stripping out the attachments,
see http://rt.perl.org/rt3/Ticket/Display.html?id=28035 for those.
Regards.
Begin forwarded message:
With input (and some code, thanks!) from Jérôme, I've made some
progress here. Both tcl and befunge should shortly be happ
What, no one's awake? =-)
I've modified my local copy of tcl, and testall so that I can now do
any of the following, e.g. from the top level parrot directory.
cd languages && make test
cd languages/tcl && make test
cd languages && ./tcl/t/cmd_append.t
cd languages/tcl && ./t/cmd_append.t
cd lang
over in perl-qa, a similar topic just came up, where Schwern answered:
{
Test::Harness just runs the tests you give it. Simplest thing to do is
to just write a little script that has the necessary logic to determine
what
set of tests to run and feed that file list to runtests().
}
However, I no
Another job for the intrepid configure and/or makefile hacker.
Right now, there's a languages-test target in the top level makefile.
This is good.
Unfortunately, the way it works is... sub-good. What it does is do a
"make test" in the languages directory, and that target runs each
language tes
16 matches
Mail list logo
