On Tuesday 01 January 2008 09:00:36 [EMAIL PROTECTED] wrote:
> Modified:
>trunk/t/tools/ops2pmutils/08-sort_ops.t
>
> Log:
> Commenting out TODO block around test for experimental.ops. Test has been
> steadily passing for > 1 month.
Why comment it out? We can revert this checkin if necessar
# New Ticket Created by Allison Randal
# Please include the string: [perl #49274]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49274 >
A quick cage cleaner task. Create a script to generate the file
ports/debian/parrot-d
Here's where we stand after r24412 on Linux.
t/dynoplibs/myops..1..10
ok 1 - fortytwo
ok 2 - what_do_you_get_if_you_multiply_six_by_nine
ok 3 - hcf
ok 4 - a short cheating quine
ok 5 - one alarm
ok 6 - three alarm
ok 7 - repeating alarm
ok 8 - bxand - A AND B, but not BOTH
ok 9 - conv_u2_i
ok
Andy Lester wrote:
It
says that time_struct below is not initialized before use, and I sure
don't see that it isn't.
Was an incorrect change, now reverted.
Allison
# New Ticket Created by James Keenan
# Please include the string: [perl #49276]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49276 >
On Dec 30, I succeeded in running 'make smoke' on my iBook for the
first time. At fir
The one remaining questionable test (concerning warning of
experimental.ops) has been passing for > 1 month. So today I commented
out the TODO block surrounding it.
I'm resolving the ticket, but please start new RT if you experience any
problems running 'perl Configure.pl --test' or 'perl Configu
The code in tools/dev/mk_manifest_and_skip.pl is mostly calls to
Parrot::Manifest methods. These are reasonably well tested in
t/manifest.t, which may be invoked after configuration as:
make manifest_tests
These tests will generate a failure if either MANIFEST or MANIFEST.SKIP
is in a state wh
With some additional refactoring of an OS-specific 'if' block and tests
to match, code coverage is extremely high, so I'm resolving this ticket.
kid51
ptc's original spec for this ticket was: "Write a SKIP block which will
test the one OS-specific branch in init::defaults."
What I have done is to isolate the OS-specific code into an internal
subroutine, _64_bit_adjustments(), and then set up mock values with
which to test that subroutine in new
Now correctly adds debian_packaging_guide.pod to the MANIFEST. New
directory structure good. Resolving.
Allison
Thanks all for the reports. I see two common trouble spots in hellgrind
and the test output. One is a possible race condition if two threads add
tasks to the concurrency scheduler at exactly the same moment. The other
is the fact that PCC uses globals in the interpreter to store invocation
info
On Jan 1, 2008, at 8:38 AM, Leopold Toetsch wrote:
struct timespec *time_struct;
This is a pointer to an unallocated structure, which was filled
thereafter.
Of course. I understand the C. It was the intent I couldn't get into.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.co
Am Dienstag, 1. Januar 2008 08:39 schrieb Andy Lester:
> Just reporting what GCC tells me, and I don't see that it's wrong. It
> says that time_struct below is not initialized before use, and I sure
> don't see that it isn't.
Fixed in 24405.
> struct timespec *time_struct;
This is a pointe
Just reporting what GCC tells me, and I don't see that it's wrong. It
says that time_struct below is not initialized before use, and I sure
don't see that it isn't.
I'd investigate further, but I'm off to bed...
xoxo,
Andy
Parrot_cx_schedule_sleep(PARROT_INTERP, FLOATVAL time,
ARGIN_NULL
chromatic schreef:
On Monday 31 December 2007 05:50:47 Allison Randal wrote:
In the concurrency work I'm about to check in, I have some tests that
fail intermittently because they test for something like:
1
alarm1
2
alarm2
3
alarm3
alarm1
alarm3
4
alarm3
alarm3
alarm3
5
done.
When the actual
15 matches
Mail list logo
