MultiThreadFailoverTest removed on build.xml

[clebert.suconic]

Andy removed it from tests on commit r5590 (which was about a wildcard fix).

so, I'm assuming it was an accident, and I'm removing the exclude clause.

However I agree those tests are taking a long time to run. Maybe we should move them to timing? I'm adding two other tests that are doing the exact same thing with Paging and LargeMessage that will take even longer.

LargeMessage and Paging are using real files, so they are supposed to take longer. I'm using less iterations.. but still a slow test.

[clebert.suconic]

Can't we make use getNumIterations()=1 on those MultiThreadFailoverTest when as part of the testsuite, and use a bigger value under stress or timing?

[clebert.suconic]

Can't we make use getNumIterations()=1 on those MultiThreadFailoverTest when as part of the testsuite, and use a bigger value under stress or timing?

I have already done it. Feel free to increase the NumIterations if you don't like it... but I think we should let the tests run faster before our checkouts, and let Hudson run the stress tests.

also... how we want to execute stress on hudson?

As part of the hourly build or should we create another build running less frequently?


It used to be part of hudson-tests, but I guess Tim removed them.

[timfox]

Don't set num iterations to 1 until you have set Hudson up to run it with 20 or more interations.

Setting it back to 20.

[clebert.suconic]

I have set the stress-tests on hudson, with 20.

So, the integration-tests are running with iterations=1.


Right now the stress-test is set to run daily at 2:00 AM EST.

Feel free to start runs manually when you do any major commits... or change the build on hudson if you feel we need it more frequently.