Mockolate internal issues

[Joshua Goodson]

Hey everyone,

I've been working on a set of flex unit tests that implement Mockolate. We have been experiencing hanging issues within some of our tests, both on our local environments and in our CI environment.

The error I am seeing is:

Error: Error #1502: A script has executed for longer than the default timeout period of 15 seconds.

at org.flemit.bytecode::ByteCodeLayout/assertEqArrayIndex()[/Volumes/Data/flemit/flemit/src/org/flemit/bytecode/ByteCodeLayout.as:732]

at org.flemit.bytecode::ByteCodeLayout/registerMultiname()[/Volumes/Data/flemit/flemit/src/org/flemit/bytecode/ByteCodeLayout.as:654]

at org.flemit.bytecode::ByteCodeLayout/registerMethodBody()[/Volumes/Data/flemit/flemit/src/org/flemit/bytecode/ByteCodeLayout.as:615]

at org.flemit.bytecode::ByteCodeLayoutBuilder/createLayout()[/Volumes/Data/flemit/flemit/src/org/flemit/bytecode/ByteCodeLayoutBuilder.as:72]

at org.floxy::ProxyRepository/prepareClasses()[/Volumes/Data/floxy/floxy/src/org/floxy/ProxyRepository.as:278]

at mockolate.ingredients.floxy::FloxyMockolateFactory/prepareClasses()[/Volumes/Data/mockolate/mockolate/src/mockolate/ingredients/floxy/FloxyMockolateFactory.as:57]

at mockolate.ingredients::Mockolatier/prepareClassRecipes()[/Volumes/Data/mockolate/mockolate/src/mockolate/ingredients/Mockolatier.as:113]

at mockolate.runner.statements::PrepareMockClasses/evaluate()[/Volumes/Data/mockolate/mockolate/src/mockolate/runner/statements/PrepareMockClasses.as:31]

at org.flexunit.internals.runners.statements::StatementSequencer/executeStep()[/Users/joshuagoodson/workspace/support/3rdparty/flexunit-master/FlexUnit4/src/org/flexunit/internals/runners/statements/StatementSequencer.as:98]

at org.flexunit.internals.runners.statements::StatementSequencer/handleChildExecuteComplete()[/Users/joshuagoodson/workspace/support/3rdparty/flexunit-master/FlexUnit4/src/org/flexunit/internals/runners/statements/StatementSequencer.as:141]

at org.flexunit.token::AsyncTestToken/sendResult()[/Users/joshuagoodson/workspace/support/3rdparty/flexunit-master/FlexUnit4/src/org/flexunit/token/AsyncTestToken.as:107]

at mockolate.runner.statements::IdentifyMockClasses/evaluate()[/Volumes/Data/mockolate/mockolate/src/mockolate/runner/statements/IdentifyMockClasses.as:59]

at org.flexunit.internals.runners.statements::StatementSequencer/executeStep()[/Users/joshuagoodson/workspace/support/3rdparty/flexunit-master/FlexUnit4/src/org/flexunit/internals/runners/statements/StatementSequencer.as:98]

at org.flexunit.internals.runners.statements::StatementSequencer/handleChildExecuteComplete()[/Users/joshuagoodson/workspace/support/3rdparty/flexunit-master/FlexUnit4/src/org/flexunit/internals/runners/statements/StatementSequencer.as:141]

at org.flexunit.internals.runners.statements::StatementSequencer/evaluate()[/Users/joshuagoodson/workspace/support/3rdparty/flexunit-master/FlexUnit4/src/org/flexunit/internals/runners/statements/StatementSequencer.as:109]

at mockolate.runner::MockolateRule/evaluate()[/Volumes/Data/mockolate/mockolate/src/mockolate/runner/MockolateRule.as:281]

at org.flexunit.internals.runners.statements::StackAndFrameManagement/handleTimerComplete()[/Users/joshuagoodson/workspace/support/3rdparty/flexunit-master/FlexUnit4/src/org/flexunit/internals/runners/statements/StackAndFrameManagement.as:138]

at flash.events::EventDispatcher/dispatchEventFunction()

at flash.events::EventDispatcher/dispatchEvent()

at flash.utils::Timer/tick()

Does anyone have any insight into why this may be occurring? I will be eternally grateful. If you need any further information from me, please don't hesitate to ask.

Thanks,

Josh

[Drew Bourne]

I've heard about this a couple of times recently. I'll dig in over the long weekend and see if I can fix it.

Could you reply to the following to help me diagnose: 

Are you using the current code in Mockolate master or one of the releases? 

Are you attempting to create proxies for any of the built-in Flash classes?

Are you extending the prototype of any built-in types? 

Are you doing any other test setup actions?

Is this happening every test run? 

When it fails like this can it be rerun successfully without recompiling? 

cheers, 

Drew

Thanks,

Josh

--
You received this message because you are subscribed to the Google Groups "Mockolate" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mockolate+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.