play.html?id=58934 >
>
>
> 'make fulltest' runs several chunks of tests, and does not show a final
> summary. So although some tests in some chunks fail, the last thing that
> the tester sees is something along these lines:
>
> ===( 35
> )=
l
summary. So although some tests in some chunks fail, the last thing that
the tester sees is something along these lines:
===( 35
)==All tests
successful.
Files=10, Tests=108, 29 wallclock secs ( 0.04 usr 0.02 sys + 19.55 cusr
1.44 csy
__cplusplus define missing
3. or due to inline/readline
4. or may be my tweaks
Regards,
Senaka
On Tue, Apr 15, 2008 at 1:45 AM, Will Coleda <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 14, 2008 at 4:00 PM, Senaka Fernando <[EMAIL PROTECTED]>
> wrote:
> > Hi all,
> >
> >
On Mon, Apr 14, 2008 at 4:00 PM, Senaka Fernando <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> C++ build succeeded, but with some tests failed. There were two issues that
> I couldn't formally sorted, and thus I had to tweak it. I have opened
> tickets for all other build r
On Fri, Mar 17, 2006 at 07:08:55PM -0600, Patrick R. Michaud wrote:
> I've just applied a change (r11921) to PGE that allows
> embedded closures in rules to designate a "return value" for
> a match (recently added to S05).
> [...]
I neglected to mention in my previous post that this update
seems t
> All extend and thread tests have passed for me on trunk with normal
> build. timer seems to pass outside the harness, but isn't happy inside
> it. Signal seems to have a 'Signal 1' message in the output which breaks
> the test.
>
> I'm just going to repeat this to double check things. I'll a
Bernhard Schmalhofer via RT wrote:
Hi,
I have applied a couple of old patches from Limbic~Region. These patches
are enabling some tests for cygwin. Unfortunately I have no cygwin
installed, so I can't tell whether the enabled tests are passing. But I
think that right after a release is a
Hi,
I have applied a couple of old patches from Limbic~Region. These patches
are enabling some tests for cygwin. Unfortunately I have no cygwin
installed, so I can't tell whether the enabled tests are passing. But I
think that right after a release is a good time for breaking things.
Coul
Craig (via RT) wrote:
Downloaded revision 8443 of Parrot to Windows XP Pro using SVN. When using
'nmake' 7.10.3077, some of the test are failing. According to the
gettingstarted.pod, none of the tests should fail.
README.win32 is more specific - dynclasses are currently broken.
Thanks, Crai
# New Ticket Created by Craig
# Please include the string: [perl #36385]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36385 >
Downloaded revision 8443 of Parrot to Windows XP Pro using SVN. When using
'nmake' 7.10.3077,
# New Ticket Created by Joshua Gatcomb
# Please include the string: [perl #29836]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=29836 >
extend 12 previously hung on Cygwin: If configured
with --intval=long and --opcode
Some tests were disabled because of recently-patched problems in the
assembler. I'm contemplating simply removing the tests that require
exceptions, because we're going to do much more with exceptions than
these (probably already deprecated) tests cover.
--
Jeff <[EMAIL PROTECTED]>
On Tue, Sep 18, 2001 at 02:14:39PM -0700, Damien Neil wrote:
> The attached file contains tests for all Parrot integer ops.
>
>- Damien
THANK YOU!
(Applied)
--
Calm down, it's *only* ones and zeroes.
The attached file contains tests for all Parrot integer ops.
- Damien
#! perl -w
use Parrot::Test tests => 26;
output_is(<
14 matches
Mail list logo
