On Jan 12, 2008, at 11:33 PM, Bob Rogers wrote:
You are advocating better marketing, which is fine -- and I am lousy
at
producing marketing copy, so I appreciate the help.
Also, it's really not that tough thinking about "marketing". All I
wrote up is enough to explain to an outside why
On Jan 12, 2008, at 11:33 PM, Bob Rogers wrote:
One line is fine for NEWS, I think.
Text is cheap. If people want to skip past it, they can. We need
to
be talking more about what we're doing. Consider the outside person
who's only vaguely, if at all, familiar with Parrot. "pbc_to
From: Andy Lester <[EMAIL PROTECTED]>
Date: Sat, 12 Jan 2008 22:29:24 -0600
On Jan 12, 2008, at 10:26 PM, Bob Rogers wrote:
> One line is fine for NEWS, I think.
Text is cheap. If people want to skip past it, they can. We need to
be talking more about what we're doing. Con
On Jan 12, 2008, at 8:29 PM, Andy Lester wrote:
We need to be talking more about what we're doing. Consider the
outside person who's only vaguely, if at all, familiar with Parrot.
"pbc_to_exe" means nothing to them.
++
---
Matisse Enz
On Jan 12, 2008, at 10:26 PM, Bob Rogers wrote:
One line is fine for NEWS, I think.
Text is cheap. If people want to skip past it, they can. We need to
be talking more about what we're doing. Consider the outside person
who's only vaguely, if at all, familiar with Parrot. "pbc_to_exe"
From: Matisse Enzer <[EMAIL PROTECTED]>
Date: Sat, 12 Jan 2008 20:20:12 -0800
Where would people here want to see buildot status messages go?
Personally, I'm not a parrot developer, so I don't have a strong
opinion.
Maybe #parrot is enough? Really, these are pretty ephemeral.
From: Andy Lester <[EMAIL PROTECTED]>
Date: Sat, 12 Jan 2008 22:14:55 -0600
On Jan 12, 2008, at 10:07 PM, Bob Rogers wrote:
> How about leading with
>
>- "make perl6" now builds a Perl6 executable
>
> as a section of its own?
It's a start, but how about this:
One
On Jan 12, 2008, at 8:15 PM, Andy Lester wrote:
On Jan 12, 2008, at 10:12 PM, jesse wrote:
What would it take to create a separate perl.org mailing list for
buildbot status messages?
Start by dropping a note to [EMAIL PROTECTED] If that doesn't
get a
response, ping me.
There's no re
On Jan 12, 2008, at 10:12 PM, jesse wrote:
What would it take to create a separate perl.org mailing list for
buildbot status messages?
Start by dropping a note to [EMAIL PROTECTED] If that doesn't
get a
response, ping me.
There's no reason that the list needs to live at perl.org. It's
On Jan 12, 2008, at 10:07 PM, Bob Rogers wrote:
How about leading with
- "make perl6" now builds a Perl6 executable
as a section of its own?
It's a start, but how about this:
--- begin ---
Parrot 0.5.2 brings a major new feature to users: The ability to build
a perl6 executable
> What would it take to create a separate perl.org mailing list for
> buildbot status messages?
Start by dropping a note to [EMAIL PROTECTED] If that doesn't get a
response, ping me.
-j
>
> -M
>
> ---
> Matisse Enzer <[EMAIL PROTECTED]>
>
On Jan 12, 2008, at 8:04 PM, jesse wrote:
At work, we actually announce all builds. passing test suites make
people feel good ;)
I'm certainly open to that.
As you might guess I am basically playing with a new toy, uh, I mean
new tool, and hoping it will be useful to the community.
I'd
From: Andy Lester <[EMAIL PROTECTED]>
Date: Sat, 12 Jan 2008 19:31:36 -0600
On Jan 12, 2008, at 4:22 PM, Bob Rogers wrote:
> - Implementation
> + New "pbc_to_exe" utility turns bytecode to executables
Please put something in the top, shouting from the rooftops, that we
ca
On Sat, Jan 12, 2008 at 07:52:00PM -0800, Matisse Enzer wrote:
> I am trying to see if I can get the ircbot to announce failed builds
> (only), with a URL for more info.
At work, we actually announce all builds. passing test suites make
people feel good ;)
> By the way, I am told someone did
On Jan 12, 2008, at 4:03 PM, jesse wrote:
So. the buildbot is a wonderful thing. But this list is probably the
wrong list to mail every single failed build to. Maybe a new list or
only annoucing them to irc?
Fair point.
I'll disable the email to this list for now.
I am trying to see if I
On Sat, Jan 12, 2008 at 08:57:11AM -0800, Cosimo Streppone wrote:
> # New Ticket Created by Cosimo Streppone
> # Please include the string: [perl #49714]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=49714 >
>
>
> This
'renumbertests' branch was merged into trunk in r24814. In addition to
renaming the tests and then editing them so that their POD refers to the
correct name, I adjusted t/harness and config/gen/makefiles/root.in to
account for creation of t/steps/ directory.
If you run the configuration tests wit
The Buildbot has detected a failed build of ubuntu-ppc-trunk.
Full details are available at:
http://buildbot.eigenstate.net:8040/ubuntu-ppc-trunk/builds/3
Buildbot URL: http://buildbot.eigenstate.net:8040/
Buildslave for this Build: ubuntu-ppc-trunk
Build Reason:
Build Source Stamp: HEAD
Blame
The Buildbot has detected a failed build of ubuntu-ppc-trunk.
Full details are available at:
http://buildbot.eigenstate.net:8040/ubuntu-ppc-trunk/builds/2
Buildbot URL: http://buildbot.eigenstate.net:8040/
Buildslave for this Build: ubuntu-ppc-trunk
Build Reason:
Build Source Stamp: HEAD
Blame
On Jan 12, 2008, at 4:22 PM, Bob Rogers wrote:
- Implementation
+ New "pbc_to_exe" utility turns bytecode to executables
Please put something in the top, shouting from the rooftops, that we
can now say "make perl6". That "pbc_to_exe" is interesting to core
people, maybe, but "make perl
The Buildbot has detected a failed build of ubuntu-ppc-trunk.
Full details are available at:
http://buildbot.eigenstate.net:8040/ubuntu-ppc-trunk/builds/1
Buildbot URL: http://buildbot.eigenstate.net:8040/
Buildslave for this Build: ubuntu-ppc-trunk
Build Reason:
Build Source Stamp: HEAD
Blame
# New Ticket Created by chromatic
# Please include the string: [perl #49722]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49722 >
The current tests in t/pmc/schedulermessage.t are only a placeholder. This
PMC needs full
On Saturday 12 January 2008 16:15:16 James Keenan wrote:
> So I'm proposing to delete the 3 digits at the start of the step
> class test files. When 'make test' runs them, they'll run in
> alphabetical order. That's okay, because each test file is logically
> independent of each other. However,
# New Ticket Created by James Keenan
# Please include the string: [perl #49720]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49720 >
Currently all the tests in t/configure/ follow one of two naming
patterns:
1. 0\d\d-
So. the buildbot is a wonderful thing. But this list is probably the
wrong list to mail every single failed build to. Maybe a new list or
only annoucing them to irc?
Best
Jesse
On Sat, Jan 12, 2008 at 03:03:37PM -0800, [EMAIL PROTECTED] wrote:
> The Buildbot has detected a failed build of ubuntu
# New Ticket Created by chromatic
# Please include the string: [perl #49718]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49718 >
At least four tests fail with the new scheduler under the JIT:
t/pmc/timer.t
The Buildbot has detected a failed build of ubuntu-ppc-trunk.
Full details are available at:
http://buildbot.eigenstate.net:8040/ubuntu-ppc-trunk/builds/0
Buildbot URL: http://buildbot.eigenstate.net:8040/
Buildslave for this Build: ubuntu-ppc-trunk
Build Reason:
Build Source Stamp: HEAD
Blame
Thanks, Josh. I'll interpret your remarks as "don't split this file up
(at least not at this time)." Closing ticket.
The 0.5.2 release is coming up this Tuesday (January 15), so I've
updated NEWS with a summary of changes since 0.5.1 based on the commit
logs, which I've also included below. Please take a look and make sure
I haven't misrepresented anything, especially in the "languages" and
"compilers" depart
On Mon Oct 22 09:34:51 2007, ptc wrote:
> In src/pmc/default.pmc:get_attr_str() there is the todo item:
>
> /* let's look for props first
> * XXX do we need that in the default object system?
>
> We require an answer to this question, and quite possibly further
> development depending upon the
General idea approved, pending review of implementation changes.
On Jan 12, 2008, at 9:42 AM, James Keenan (via RT) wrote:
# New Ticket Created by James Keenan
# Please include the string: [perl #49668]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49668 >
Test file t/op/jit.t currentl
All PDD tickets and all found design tickets moved to Launchpad. Please
submit design requests to https://blueprints.launchpad.net/parrot/.
jerry gay ha scritto:
On Jan 9, 2008 12:08 AM, Cosimo wrote:
I'm trying to play with perl6.exe.
I've wandered in the opened tickets for perl6 and
saw this one about `substr()':
http://rt.perl.org/rt3/Public/Bug/Display.html?id=44321
what we ultimately want is tests that cover the spec, which
chromatic, go ahead and apply this in the pdd17pmc branch. Was already
updated in docs/dev/pccmethod.pod. I'm noting the change in DEPRECATED.pod.
Author: allison
Date: Sat Jan 12 11:02:24 2008
New Revision: 24800
Removed:
trunk/docs/pdds/draft/pdd12_assembly.pod
Changes in other areas also in this revision:
Modified:
trunk/MANIFEST
Log:
[pdd] Deleting unused placeholder PDD, number may be reclaimed for other uses.
Thanks, applied as r24799
On Saturday 12 January 2008 06:16:14 James E Keenan wrote:
> We can overcome this difficulty to a considerable extent by refactoring
> that mocks the conditions found on various OS/platform/compiler
> combinations. Even if we're not on a Windows box, we can write tests
> that ask, "Suppose that w
# New Ticket Created by Cosimo Streppone
# Please include the string: [perl #49714]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49714 >
This is a patch to modify `make spectest' target
for languages/perl6 to fetch also n
I had no feedback on this refactoring, but I got no complaints either.
No smoke tests failed. Resolving ticket.
# New Ticket Created by James Keenan
# Please include the string: [perl #49712]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49712 >
Test file t/pmc/nci.t currently (r24787) has 2649 lines.
Examine this file and determin
# New Ticket Created by James Keenan
# Please include the string: [perl #49710]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49710 >
Test file t/pmc/objects.t currently (r24787) has 2083 lines.
Examine this file and dete
# New Ticket Created by James Keenan
# Please include the string: [perl #49708]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49708 >
Test file t/pmc/namespace.t currently (r24787) has 1720 lines.
Examine this file and de
# New Ticket Created by James Keenan
# Please include the string: [perl #49706]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49706 >
Test file t/pmc/mmd.t currently (r24787) has 1450 lines.
Examine this file and determin
# New Ticket Created by James Keenan
# Please include the string: [perl #49704]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49704 >
Test file t/op/string.t currently (r24787) has 2907 lines.
Examine this file and determ
# New Ticket Created by James Keenan
# Please include the string: [perl #49702]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49702 >
Test file t/pmc/float.t currently (r24787) has 1154 lines.
Examine this file and determ
# New Ticket Created by James Keenan
# Please include the string: [perl #49700]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49700 >
Test file t/pmc/object-meths.t currently (r24787) has 1269 lines.
Examine this file and
On Thu Jan 10 17:48:44 2008, [EMAIL PROTECTED] wrote:
> On Thu Jan 10 13:38:26 2008, coke wrote:
> > Looks good, thanks! A few minor minor nits which are just book-keeping
> > tasks:
>
> Thanks for the feedback. I've cleaned up those book-keeping items as
> well as fixed a couple of end's that sho
Thanks, Applied as r24790
# New Ticket Created by James Keenan
# Please include the string: [perl #49698]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49698 >
Test file t/pmc/string.t currently (r24787) has 1372 lines.
Examine this file and deter
I have created RT tickets for 25 test files each of which is >= 1000
lines in length. The tickets ask you to examine the file to determine
whether it can reasonably be subdivided. If so, subdivide; if not, take
and resolve the ticket.
2907 t/op/string.t
2649 t/pmc/nci.t
2485 t/op/calling.t
# New Ticket Created by James Keenan
# Please include the string: [perl #49694]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49694 >
Test file t/op/integer.t currently (r24787) has 1387 lines.
Examine this file and deter
# New Ticket Created by James Keenan
# Please include the string: [perl #49696]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49696 >
Test file t/pmc/resizablepmcarray.t currently (r24787) has 1230 lines.
Examine this fil
# New Ticket Created by James Keenan
# Please include the string: [perl #49692]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49692 >
Test file t/op/cmp-nonbranch.t currently (r24787) has 1206 lines.
Examine this file and
# New Ticket Created by James Keenan
# Please include the string: [perl #49690]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49690 >
Test file t/pmc/threads.t currently (r24787) has 1151 lines.
Examine this file and dete
# New Ticket Created by James Keenan
# Please include the string: [perl #49688]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49688 >
Test file t/pmc/sub.t currently (r24787) has 1477 lines.
Examine this file and determin
# New Ticket Created by James Keenan
# Please include the string: [perl #49686]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49686 >
Test file t/library/streams.t currently (r24787) has 1467 lines.
Examine this file and
# New Ticket Created by James Keenan
# Please include the string: [perl #49684]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49684 >
Test file t/op/number.t currently (r24787) has 1238 lines.
Examine this file and determ
# New Ticket Created by James Keenan
# Please include the string: [perl #49682]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49682 >
Test file t/op/lexicals.t currently (r24787) has 1251 lines.
Examine this file and dete
# New Ticket Created by James Keenan
# Please include the string: [perl #49680]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49680 >
Test file t/pmc/bigint.t currently (r24787) has 1141 lines.
Examine this file and deter
# New Ticket Created by James Keenan
# Please include the string: [perl #49678]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49678 >
Test file t/pmc/complex.t currently (r24787) has 1907 lines.
Examine this file and dete
# New Ticket Created by James Keenan
# Please include the string: [perl #49676]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49676 >
Test file t/pmc/hash.t currently (r24787) has 1433 lines.
Examine this file and determi
# New Ticket Created by James Keenan
# Please include the string: [perl #49674]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49674 >
Test file t/pmc/iterator.t currently (r24787) has 1433 lines.
Examine this file and det
The Buildbot has detected a failed build of Parrot-Builder-trunk.
Full details are available at:
http://buildbot.eigenstate.net:8040/Parrot-Builder-trunk/builds/43
Buildbot URL: http://buildbot.eigenstate.net:8040/
Buildslave for this Build: parrot-bot1
Build Reason:
Build Source Stamp: HEAD
B
# New Ticket Created by James Keenan
# Please include the string: [perl #49672]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49672 >
Test file t/pmc/resizablestringarray.t currently (r24787) has 1381 lines.
Examine this
# New Ticket Created by James Keenan
# Please include the string: [perl #49670]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49670 >
Test file t/op/calling.t currently (r24787) has 2485 lines.
Examine this file and deter
# New Ticket Created by James Keenan
# Please include the string: [perl #49668]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=49668 >
Test file t/op/jit.t currently (r24787) has 1274 lines.
Examine this file and determine
On 11 Jan 2008, at 18:25, [EMAIL PROTECTED] wrote:
I've fixed the incompatibility in Test::Harness's handling of @INC
propagation to the test script. It now behaves like 2.64. Parrot's
tests now run without these errors.
The changes will show up in Test::Harness 3.02 which will probably be
relea
The Buildbot has detected a failed build of Parrot-Builder-trunk.
Full details are available at:
http://buildbot.eigenstate.net:8040/Parrot-Builder-trunk/builds/42
Buildbot URL: http://buildbot.eigenstate.net:8040/
Buildslave for this Build: parrot-bot1
Build Reason:
Build Source Stamp: HEAD
B
The Buildbot has detected a failed build of Parrot-Builder-trunk.
Full details are available at:
http://buildbot.eigenstate.net:8040/Parrot-Builder-trunk/builds/41
Buildbot URL: http://buildbot.eigenstate.net:8040/
Buildslave for this Build: parrot-bot1
Build Reason:
Build Source Stamp: HEAD
B
chromatic wrote:
On Friday 11 January 2008 16:44:58 [EMAIL PROTECTED] wrote:
Log:
auto::msvc: Refactored some code to increase testability:
_handle_not_msvc(). Add 113-auto_msvc-04.t to test this internal
subroutine. In 113-auto_msvc-01.t, SKIP only test for runstep() on
non-Win32 platforms.
The Buildbot has detected a failed build of Parrot-Builder-trunk.
Full details are available at:
http://buildbot.eigenstate.net:8040/Parrot-Builder-trunk/builds/40
Buildbot URL: http://buildbot.eigenstate.net:8040/
Buildslave for this Build: parrot-bot1
Build Reason:
Build Source Stamp: HEAD
B
On Nov 15 2007, 1:40 pm, [EMAIL PROTECTED] (Andy Armstrong) wrote:
> On 14 Nov 2007, at 22:13, Patrick R.Michaud (via RT) wrote:
>
> > Last week I had to reinstall the OS on my desktop, and after
> > installing Test::TAP::HTMLMatrix (for 'make smoke') I now get
> > a lot of errors during 'make test
Supplied through 'inspect' and 'inspect_str' vtable functions.
James Keenan via RT schrieb:
Hey, gang! Can anyone comment on the status of this ticket?
I agree that if a test file is 2400 lines long, there's a prima facie
case for splitting it into smaller components.
However, based on my experience and ptc's in cage-cleaning, I'd
recommend opening up ind
James Keenan via RT schrieb:
On Sun Oct 02 05:22:08 2005, [EMAIL PROTECTED] wrote:
config/gen/makefiles/root.in already weighs in at 1581 lines. It needs
to be divided up into smaller files that are combined when Configure is
run.
Apart from the fact that it's a PITA to edit a file w
76 matches
Mail list logo
