[Top][All Lists]

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

[Gnash-commit] [patch #8770] Patch for adding JavaScript-calls-Flash Ext

From: Sandro Santilli
Subject: [Gnash-commit] [patch #8770] Patch for adding JavaScript-calls-Flash ExternalInterface automated testcase
Date: Fri, 20 Nov 2015 10:38:10 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0

Follow-up Comment #1, patch #8770 (project gnash):

I'm trying to run the test as part of "make check" but finding it to fail when
invoked via bash. Still, "make check" does not show any failure.

The runtest call I see happening (after removing the '@' sign from the
check-DEJAGNU Makefile rule):

make check
make  check-DEJAGNU
make[1]: Entering directory
runtest=runtest; \
        if /bin/bash -c "$runtest --version" > /dev/null 2>&1; then \
            GNASH_GC_TRIGGER_THRESHOLD=0  GNASHRC=../gnashrc $runtest 
../simple.exp; true; \
        else \
          echo "WARNING: could not find \`runtest'" 1>&2; \
          for i in "sanetests-runner bogustests-runner extcommtests-runner ";
do \
            GNASH_GC_TRIGGER_THRESHOLD=0  GNASHRC=../gnashrc /bin/bash $i; \
          done; \
WARNING: No tool specified
Test Run By strk on Fri Nov 20 11:31:55 2015
Native configuration is x86_64-unknown-linux-gnu

                ===  tests ===

Schedule of variations:

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
Using /usr/share/dejagnu/config/unix.exp as generic interface file for
WARNING: Couldn't find tool config file for unix, using default.
Running /usr/src/gnash/gnash-head/testsuite/misc-mtasc.all/../simple.exp ...

                ===  Summary ===

# of expected passes            193
# of expected failures          2
make[1]: Leaving directory

If I only keep the extcommtests-runner in TEST_CASES, I get:

 Running /usr/src/gnash/gnash-head/testsuite/misc-mtasc.all/../simple.exp ...

                ===  Summary ===

 # of expected passes            9

But running the test manually:

extcommtests-runner > /tmp/log

I see an early failure:

 FAILED: Gnash should return a correct value from ExternalInterface callback
("<invoke name="addMethod"
!= "<string>Too</string>")

and other 8 successes.

Ideas about why there's such difference ?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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