On Wed, Jul 2, 2008 at 11:06 PM, chromatic <[EMAIL PROTECTED]> wrote:
>$ parrot perl6.pbc --output=buggy.pir --trace=PIR buggy.p6
>
s/trace/target/
On Sunday 29 June 2008 16:16:13 Moritz Lenz wrote:
> > They almost definitely won't get fixed unless they're reported, and they
> > probably won't get fixed without simpler PIR examples.
>
> So how do we get simpler PIR examples?
Sometimes running:
$ parrot perl6.pbc --output=buggy.pir -
chromatic wrote:
> On Sunday 29 June 2008 15:03:24 Moritz Lenz wrote:
>
>> I know of #55782. From time to time I encounter some GC weirdnesses, but
>> so far I didn't care to report them all, because I have no way of to
>> know if they have all the same root or not.
>
>> And as long as even the s
On Sun, Jun 29, 2008 at 02:21:20PM -0700, chromatic wrote:
> On Sunday 29 June 2008 06:52:12 [EMAIL PROTECTED] wrote:
> > --- trunk/languages/perl6/tools/test_summary.pl (original)
> > +++ trunk/languages/perl6/tools/test_summary.pl Sun Jun 29 06:52:09 2008
> > @@ -58,7 +58,7 @@
> > -my
On Sunday 29 June 2008 15:03:24 Moritz Lenz wrote:
> I know of #55782. From time to time I encounter some GC weirdnesses, but
> so far I didn't care to report them all, because I have no way of to
> know if they have all the same root or not.
> And as long as even the simplest programs in rakudo
chromatic wrote:
> On Sunday 29 June 2008 06:52:12 [EMAIL PROTECTED] wrote:
>
>> Modified:
>>trunk/languages/perl6/tools/test_summary.pl
>>
>> Log:
>> [rakudo]:
>> * Update test_summary.pl script to use -G,
>> record aborted test runs as failed tests.
>> Modified: trunk/languages/perl6/tools
On Sunday 29 June 2008 06:52:12 [EMAIL PROTECTED] wrote:
> Modified:
>trunk/languages/perl6/tools/test_summary.pl
>
> Log:
> [rakudo]:
> * Update test_summary.pl script to use -G,
> record aborted test runs as failed tests.
> Modified: trunk/languages/perl6/tools/test_summary.pl
> ==
