gnash-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-dev] make check failing to finish


From: dolphinling
Subject: Re: [Gnash-dev] make check failing to finish
Date: Sun, 13 May 2007 17:01:20 -0400
User-agent: Thunderbird 2.0.0.0 (X11/20070326)

dolphinling wrote:
strk wrote:
On Sun, May 13, 2007 at 06:08:51AM -0400, dolphinling wrote:
Actually, here's more output. Could it be because I have ming 0.3.0?

Yep, that's it. Number.as fails to use the macro it should:

in check.as:
#if MING_VERSION_CODE >= 00040003
# define MING_SUPPORTS_ASM
...

So any block of testts using the 'asm {... }' should be
in an #ifdef MING_SUPPORTS_ASM block.

Willing to give it a try till it completes and send a patch ?
(it would be easier for you as we are running more recent Ming
versions in order to be able to produce more precise testcases..)


I committed a fix for Number.as. If any other file fails due
to use of 'asm' syntax you may copy the ifdef lines over and
send a patch.
Thanks.
--strk;

With just that fix, it completes now :) Now, it's not giving any results... but at least it completes! (That's probably because I don't have dejagnu, though, getting that now.)

Hmm... with dejagnu installed it gets stuck in an infinite loop somewhere

XPASS: get_frame_number_testrunner: _currentframe == 3 [get_frame_number_test.c:162] FAIL: get_frame_number_testrunner: expected: 6 obtained: 7 [get_frame_number_test.c:70] FAIL: get_frame_number_testrunner: expected: 2 obtained: 7 [get_frame_number_test.c:72] FAIL: get_frame_number_testrunner: expected: 2 obtained: 1 [get_frame_number_test.c:74] FAIL: get_frame_number_testrunner: expected: 2 obtained: 1 [get_frame_number_test.c:76] FAIL: get_frame_number_testrunner: expected: 2 obtained: 1 [get_frame_number_test.c:78] FAIL: get_frame_number_testrunner: expected: 2 obtained: 7 [get_frame_number_test.c:81] FAIL: get_frame_number_testrunner: expected: 2 obtained: 7 [get_frame_number_test.c:84] FAIL: get_frame_number_testrunner: expected: 5 obtained: 4 [get_frame_number_test.c:87] FAIL: get_frame_number_testrunner: expected: 5 obtained: 6 [get_frame_number_test.c:90] FAIL: get_frame_number_testrunner: expected: 3 obtained: 1 [get_frame_number_test.c:124] FAIL: get_frame_number_testrunner: expected: 4 obtained: 1 [get_frame_number_test.c:127] FAIL: get_frame_number_testrunner: expected: 1 obtained: 7 [get_frame_number_test.c:137] FAIL: get_frame_number_testrunner: expected: 5 obtained: 7 [get_frame_number_test.c:145] FAIL: get_frame_number_testrunner: expected: 4 obtained: 3 [get_frame_number_test.c:152]

repeated over and over and over again.

This doesn't happen with ming 0.4.0beta4. Is it worth trying to get past this (perhaps because most distros don't ship the beta), or should I just forget about it and use 0.4?

--
dolphinling
<http://dolphinling.net/>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]