7 Commits

Author	SHA1	Message	Date
antirez	4f4676a142	Fix test false positive introduced by threaded I/O. ... Now clients that are ready to be terminated asynchronously are processed more often in beforeSleep() instead of being processed in serverCron(). This means that the test will not be able to catch the moment the client was terminated, also note that the 'omem' figure now changes in big steps, because of the new client output buffers layout. So we have to change the test range in order to accomodate for that. Yet the test is useful enough to be worth taking, even if its precision is reduced by this commit. Probably if we get more problems, a thing that makes sense is just to check that the limit is < 200k. That's more than enough actually.	2019-05-13 17:27:10 +02:00
antirez	797d98e906	Test: obuf-limits test false positive removed. ... Fixes #621.	2013-03-25 11:56:34 +01:00
antirez	fcdeb98568	even less false positive on obuf-limits test.	2012-02-22 11:25:30 +01:00
antirez	fc4ed4299b	minimal change to obuf-limits.tcl test to make sure there are no false positives with 32bit instances as well.	2012-01-30 21:08:10 +01:00
antirez	7f7a13b27b	Less false positives for obuf-limits.tcl tests	2012-01-26 16:08:24 +01:00
antirez	da9c4cc147	Added test for client output buffer limit (soft limit).	2012-01-25 18:34:56 +01:00
antirez	efc8f6c1a2	Added test for client output buffer limit (hard limit).	2012-01-25 18:11:04 +01:00