For some unknown reason the Stubs.SimpleStubTests.test_writeToStub test runs nearly instantly if it is run alone or as the first test. However, if it doesn't run first or alone then it takes over 5 seconds.
The issue was that the test was using lousy.stubs.newest, which was returning the old last created stub. The test was still passing because of another bug where all stubs shared on pair of in/out buffers.
For some unknown reason the Stubs.SimpleStubTests.test_writeToStub test runs nearly instantly if it is run alone or as the first test. However, if it doesn't run first or alone then it takes over 5 seconds.
Date: 2014-02-06 06:13:33
User: travisb
The issue was that the test was using lousy.stubs.newest, which was returning the old last created stub. The test was still passing because of another bug where all stubs shared on pair of in/out buffers.