|
From: | George Thomas |
Subject: | [Gnash-commit] [patch #8086] RTMP netStream patch |
Date: | Wed, 31 Jul 2013 11:52:16 +0000 |
User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:21.0) Gecko/20100101 Firefox/21.0 |
Follow-up Comment #6, patch #8086 (project gnash): Ran the regressing with the source checked out today. Could not find any regressions when tested with and without rtmp2.patch As regressions are absent is this good enough to go in or what work would have to be done to ensure that the patch is better? I was getting these failures in both cases. Test Result Totals: Total passes: 47631 Total unresolved: 9 Total expected failures: 1334 Total untested: 423 * Total real failures: 6 Unexpected failures follow: --=[ testsuite/actionscript.all ]=-- FAIL: astests-v6-Runner: no onSoundComplete arrived after 3 seconds FAIL: astests-v6-Runner: Tests run 107 (expected 112) [ [../../../gnash/testsuite/actionscript.all/Sound.as:31]] FAIL: astests-v7-Runner: no onSoundComplete arrived after 3 seconds FAIL: astests-v7-Runner: Tests run 107 (expected 112) [ [../../../gnash/testsuite/actionscript.all/Sound.as:31]] FAIL: astests-v8-Runner: no onSoundComplete arrived after 3 seconds FAIL: astests-v8-Runner: Tests run 107 (expected 112) [ [../../../gnash/testsuite/actionscript.all/Sound.as:31]] Could not understand why these were happening. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/patch/?8086> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |