Thanks Mike! engine.dispose() fixed it. Makes sense that it was a garbage
collection problem.
For any others finding this, I just added a call to engine.dispose() to
class level tearDown and it's all good.
On Thu, Sep 8, 2016 at 10:39 AM, Iain Duncan
wrote:
> I've discovered too that the issue
I've discovered too that the issue only happens when all my test suites get
called from one call to discovery. I've I run then in 8 calls (one to each
package, with each holding 1 to 5 test suites of about 1 to 10 tests each),
there's no issue. :-/
iain
On Thu, Sep 8, 2016 at 10:36 AM, Iain Dunca
Thanks Mike, no we aren't. I think we are just making a new engine per
suite, not per test though, we have the engine init code in the class level
setup function, and per test setUp is making new sessions. We do drop the
tables per test, which I expect we are not doing correctly as I'm a
postgres n
Engine per test is v inefficient, are you at least calling dispose() on
each one in teardown?
On Thursday, September 8, 2016, Iain Duncan
wrote:
> Hi Jonathan, sure can, here it is below. I think maybe this has something
> to do with the fact that we are creating a new engine and dropping the
>
Hi folks, I'm not sure if this is the right place to ask really. I have
some functional tests, using webtest, in which I make an engine and make a
couple of session that get used in addition to the webtest app. I close the
sessions in the tearDown method after each test.
Now that the number of fun
