# New Ticket Created by Simon Glover
# Please include the string: [perl #19143]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=19143 >
I've managed to track down the cause of the failure of at least one of
the properties
On Sat, Dec 14, 2002 at 06:51:19PM -0500, Simon Glover wrote:
>
> I've just commited the appended fix, which should hopefully reduce the
> number of failures in the Tinderbox.
Brilliant! A FreeBSD box I've got access to is now much happier.
Previously many many things were failing.
[Not perfec
I've just commited the appended fix, which should hopefully reduce the
number of failures in the Tinderbox.
Simon
--- interpreter.c.old Sat Dec 14 18:26:45 2002
+++ interpreter.c Sat Dec 14 18:44:49 2002
@@ -591,7 +591,7 @@ Parrot_really_destroy(int exit_code, voi
chunks[1] =
On Sat, Dec 14, 2002 at 05:14:15PM -0500, Dan Sugalski wrote:
> It crashes rather badly in a number of spots on OS X, unfortunately.
> I've also noticed that we have no Win32 systems in the tinderbox. Are
> we building OK on Win32 anywhere?
s/Win32//g :-(
*percy* parrot 5 red, 14 orange, 0 gr
At 12:44 PM -0800 12/14/02, Steve Fink wrote:
I notice that the current tree doesn't pass the tests even on my
rather forgiving machine, so there's some work to do. :-) (MANIFEST is
broken again, and nci.t is failing. I'll fix the first now.)
It crashes rather badly in a number of spots on OS X,
On Sat, 14 Dec 2002, Steve Fink wrote:
> I notice that the current tree doesn't pass the tests even on my
> rather forgiving machine, so there's some work to do. :-) (MANIFEST is
> broken again, and nci.t is failing. I'll fix the first now.)
nci.t has started failing because we're only skipping
The Parrot tree is now frozen in preparation for the 0.0.9 release.
That means no new features. Bugfixes and warnings eliminations are
still acceptable.
If anyone messes up and commits any feature-related changes between
now and Wednesday, I'll back the changes out and open a ticket, so I
(or some
At 8:23 PM +0100 12/14/02, Leopold Toetsch wrote:
[EMAIL PROTECTED] wrote:
Dan --
The first cut at native call stuff via thunks is in. It is kind of
working, but
the test I'm using (a translation of acme's life.pasm) isn't working yet,
and when I try to debug by watching parrot -t, it behaves
[EMAIL PROTECTED] wrote:
Dan --
The first cut at native call stuff via thunks is in. It is kind of
working, but
the test I'm using (a translation of acme's life.pasm) isn't working yet,
and when I try to debug by watching parrot -t, it behaves differently
than otherwise (Heisenbug!).
I have no
[EMAIL PROTECTED] wrote:
Dan --
The first cut at native call stuff via thunks is in. It is kind of
working, but
the test I'm using (a translation of acme's life.pasm) isn't working yet,
and when I try to debug by watching parrot -t, it behaves differently
than otherwise (Heisenbug!).
I have no
[EMAIL PROTECTED] wrote:
Dan --
The first cut at native call stuff via thunks is in. It is kind of
working, but
the test I'm using (a translation of acme's life.pasm) isn't working yet,
and when I try to debug by watching parrot -t, it behaves differently
than otherwise (Heisenbug!).
To say i
At 6:14 AM -0500 12/14/02, [EMAIL PROTECTED] wrote:
Dan --
The first cut at native call stuff via thunks is in. It is kind of
working, but
the test I'm using (a translation of acme's life.pasm) isn't working yet,
and when I try to debug by watching parrot -t, it behaves differently
than otherwise
Dan --
The first cut at native call stuff via thunks is in. It is kind of
working, but
the test I'm using (a translation of acme's life.pasm) isn't working yet,
and when I try to debug by watching parrot -t, it behaves differently
than otherwise (Heisenbug!).
Along the way, I added some argument
13 matches
Mail list logo
