Otherwise, we would check the same chunk multiple times, if last range
check was successful: at this point, we wouldn't know criterion to find
the first row after replicated chunk.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2411 71dcc9de-d417-0410-9af5-da40c76e7ee4

This caused incorrect object deletions during replication, when a chunk
lacks rows.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2410 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2409 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2408 71dcc9de-d417-0410-9af5-da40c76e7ee4

deleteTransaction is used by replication to remove a single transaction but
not its content.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2407 71dcc9de-d417-0410-9af5-da40c76e7ee4

Otherwise, it might not be called (it connector is not present at
transaction manager's "begin" call time).

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2406 71dcc9de-d417-0410-9af5-da40c76e7ee4

If current chunk size is lesser than maximum, it means latest check for the
whole chunk found a problem. If current smaller check succeeded, move to
the other half and divide size by two.
Also, factorise replication "check...Range" handlers.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2405 71dcc9de-d417-0410-9af5-da40c76e7ee4

This way, it is clear that test doesn't expect replication to end after
current chunk.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2404 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2403 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2402 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2401 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2400 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2399 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2398 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2397 71dcc9de-d417-0410-9af5-da40c76e7ee4

This prevents lines from next setUp from showing up in test's log.
This is not so nice to have to call it here, but it is probably an
artificial-enough use case to justify this.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2396 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2395 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2394 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2393 71dcc9de-d417-0410-9af5-da40c76e7ee4

There is no reason why we wouldn't see this when runing individual
tests, I think.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2392 71dcc9de-d417-0410-9af5-da40c76e7ee4

Also, improve exit condition readability.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2391 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2390 71dcc9de-d417-0410-9af5-da40c76e7ee4

Was enabled accidentally in r2371.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2389 71dcc9de-d417-0410-9af5-da40c76e7ee4

But make it optional, as some tests might want to stop everything
except clients (stopping single processes is already possible
separately).

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2388 71dcc9de-d417-0410-9af5-da40c76e7ee4

Call it in client, right after starting and stopping poll thread.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2387 71dcc9de-d417-0410-9af5-da40c76e7ee4

Fixes thread flood in ZODB tests (at least).

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2386 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2385 71dcc9de-d417-0410-9af5-da40c76e7ee4

It usually happens when tests are stuck, and we want to know where it
was stuck.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2384 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2383 71dcc9de-d417-0410-9af5-da40c76e7ee4

This is because verification handler doesn't implement responses to
questions sent by a storage node after it receives the order to start.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2382 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2381 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2380 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2379 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2378 71dcc9de-d417-0410-9af5-da40c76e7ee4

This makes it easier to control logging in runner (otherwise, would
go to stderr) and functional tests (directed to its own file).

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2377 71dcc9de-d417-0410-9af5-da40c76e7ee4

This was broken by r2371: it is good not to import it at file top-level,
but it must still be provided.
Also, fix 'No handler could be found for logger "NEO"' error messages,
which where hiding log messages, by using setupLog.
Also, manually set propagate to 0 so NEO messages are not output by root
logger too.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2376 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2375 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2374 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2373 71dcc9de-d417-0410-9af5-da40c76e7ee4

This is most efficient (kernel knows what's available) & cleaner.

Of course, this is not perfect either. Still, it solved many "port already
in use" happening for me with previous implementation, for some reason.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@2372 71dcc9de-d417-0410-9af5-da40c76e7ee4