1d020f1c116ce86af2ebd108a453f7bb31240ada |
|
10-Jul-2014 |
Phil Carmody <phil@dovecot.fi> |
lib: test-istream-concat - add simultanious limit streams back into the mix
Return to the previous complex nested stream-type case.
1 time in 10, it tests the simple case of:
test_stream \
test_stream -}- concat_stream
test_stream /
(2-11 of these)
9 times in 10, it tests this configuration instead:
test_stream \ / limit_stream
test_stream -}- concat_stream {- limit_stream
test_stream / \ limit_stream
(2-11 of these) (1-9 of these)
Since 31efe2d04793 lib: istream-concat read() returned -2 too early., all tests
pass every time.
Signed-off-by: Phil Carmody <phil@dovecot.fi> |
a028ac787d8fdfb3df0b878109650a25ce7a38db |
|
10-Jul-2014 |
Phil Carmody <phil@dovecot.fi> |
lib: test-istream-concat - test only concat, not simultanious limit streams
Test just concat functionality in this unit test. Simultanious access of
limit streams can be tested elsewhere.
Without the fix in:
31efe2d04793 lib: istream-concat read() returned -2 too early.
The failure previously seen in test-istream-concat would be still reproducable:
test-istream-concat.c:84: Assert failed: size >= TEST_MAX_BUFFER_SIZE
istream concat random ................................................ : FAILED
test: random seed #1 was 1403118493
Signed-off-by: Phil Carmody <phil@dovecot.fi> |
dd8a8566def603776cc102ec86906556b8bd5b0a |
|
27-Jun-2014 |
Phil Carmody <phil@dovecot.fi> |
lib: remove unwanted srand()s from unit tests
We'll get better coverage without them.
Note: this change causes the following test case failure occasionally:
test-istream-concat.c:88: Assert failed: size >= TEST_MAX_BUFFER_SIZE
istream concat random ................................................ : FAILED
test: random seed #1 was 1403027537
(The seed may vary, obviously.)
Signed-off-by: Phil Carmody <phil@dovecot.fi> |