How do I increase the timeout for tests.

[DL]

I'm currently running into the 15 seconds default timeout period. How
do I increase it for tests that take longer than 15 seconds.

I'm currently comparing large datasets

[DL]

Anyone? Still haven't any idea how I can increase this default timeout.

[Matt Hughes]

This is a timeout that the TestCase is giving?  Or the TestRunner?  You might get better results if you give a bit more information.  Maybe a stack trace of the failing test...

[DL]

I believed it's the test runner. It's happening because the total
time to run the test is exceeding 15 seconds. I believe there's got
to be some sort of parameter, or some constant I can alter to
recompile Fluint to get around this 15 second limitation. I have no
clue where this 15 seconds is coming from. I'm starting to suspect it
might be something done by the Air/Flash Plugin environment itself.

Error: Error #1502: A script has executed for longer than the default
timeout period of 15 seconds.
at mx.utils::ObjectUtil$/compareResult()[E:\dev\gumbo_alpha\frameworks
\projects\framework\src\mx\utils\ObjectUtil.as:1222]
at mx.utils::ObjectUtil$/internalCompare()[E:\dev\gumbo_alpha
\frameworks\projects\framework\src\mx\utils\ObjectUtil.as:706]
at mx.utils::ObjectUtil$/compare()[E:\dev\gumbo_alpha\frameworks
\projects\framework\src\mx\utils\ObjectUtil.as:79]
at testUtils::TestImageUtils$/imageCompare()[c:\someproduct
\IntegrationTests\src\testUtils\(redacted).as:179]
at screenRendererSuite.tests::ScreenRendererTest2/assertHandler()[c:
\someproduct\IntegrationTests\src\testSuite\tests\Test2.as:239]
at net.digitalprimates.fluint.sequence::SequenceRunner/applyHandlers()
[C:\temp\fluintrc2\1.1RC2\fluint\src\main\flex\net\digitalprimates
\fluint\sequence\SequenceRunner.as:147]
at net.digitalprimates.fluint.sequence::SequenceRunner/
continueSequence()[C:\temp\fluintrc2\1.1RC2\fluint\src\main\flex\net
\digitalprimates\fluint\sequence\SequenceRunner.as:187]
at net.digitalprimates.fluint.tests::TestCase/handleNextSequence()[C:
\temp\fluintrc2\1.1RC2\fluint\src\main\flex\net\digitalprimates\fluint
\tests\TestCase.as:388]
at Function/http://adobe.com/AS3/2006/builtin::apply()
... (rest is redacted as it contains references to company
confidential code)

[Matt Hughes]

http://livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/flash/errors/ScriptTimeoutError.html

Don't think this has anything to do with Fluint.  You have some code (looks like in your assert handler) that is never advancing.

[Michael Labriola]

I don't think that is the real cause of the issue.

So, first, the 15 second thing is coming from Flash Player. Flash runs
in a series of frames and, if any single execution thread.. let's just
say fram at this point (which is usually a 1/24th ish of a second)
takes up to 15 it believes something is wrong. It is likely right.

Fluint breaks up your tests so that they run in separate frames so
that this does not occur. However, Flash Player is not multi-threaded
from our perspective so we can't actually interrupt any code that is
executing. That means that a single test in your code right now is
trying to take more than 15 seconds to run without giving back
control.

There is nothing we can do to change that timeout, flash player
imposes it as a sanity check. Looking at your post it seems like you
might be caught in some type of loop (perhaps infinite). Any chance
you can poke around with commenting out some of these tests to narrow
it down?

If you are using the flex debugger, it might be useful to hit the
pause buttons a few times during the tests to figure out where it is
stuck.

We actually have test suites here that take 6 or 7 hours to run, so it
is not the whole length of the testing, but rather an individual
method causing the issue,
Mike

[Michael Labriola]

Also, just read the rest of your post. If the dataset is that large
that your are comparing, you are likely going to need to break this
across multiple tests. You just can't do that much in one frame
without flash complaining, it is not multi-threaded from the
developers side, so everything locks while you are doing this work

> > confidential code)- Hide quoted text -
>
> - Show quoted text -