[Dovecot] dovecot 2.0 fails self-tests
Hi,
is it expected that dovecot 2.0.beta4 pass all of it's self-tests or some failures are normal?
I've tried make check and everything passed up to this test:
...
message_date_parse(7) ................................................ : ok
0 / 8 tests failed
test-message-decoder.c:67: Assert failed:
message_decoder_decode_next_block(ctx, &input, &output)
test-message-decoder.c:78: Assert failed: output.size == 3
test-message-decoder.c:84: Assert failed: output.size == 14
test-message-decoder.c:85: Assert failed: memcmp(output.data, "
bar", 14) == 0
message decoder ...................................................... :
FAILED
1 / 1 tests failed
Regards, Michal Hlavinka
On Fri, 2010-03-26 at 14:13 +0100, Michal Hlavinka wrote:
Hi,
is it expected that dovecot 2.0.beta4 pass all of it's self-tests or some failures are normal?
Tarballs are built with "make distcheck", which would fail if any of the self-tests failed.
message_date_parse(7) ................................................ : ok 0 / 8 tests failed test-message-decoder.c:67: Assert failed: message_decoder_decode_next_block(ctx, &input, &output)
I can't reproduce this with Debian/64bit, Centos/32bit 5.4 or Solaris/Sparc.
On Fri, 2010-03-26 at 16:28 +0200, Timo Sirainen wrote:
message_date_parse(7) ................................................ : ok 0 / 8 tests failed test-message-decoder.c:67: Assert failed: message_decoder_decode_next_block(ctx, &input, &output)
I can't reproduce this with Debian/64bit, Centos/32bit 5.4 or Solaris/Sparc.
And then immediately thought of valgrind:
==18666== Conditional jump or move depends on uninitialised value(s) ==18666== at 0x402AFF: message_decoder_decode_next_block (message-decoder.c:148)
Yeah, looks like there's a bug.
On Fri, 2010-03-26 at 16:29 +0200, Timo Sirainen wrote:
==18666== Conditional jump or move depends on uninitialised value(s) ==18666== at 0x402AFF: message_decoder_decode_next_block (message-decoder.c:148)
Yeah, looks like there's a bug.
Well, that was a simple fix: http://hg.dovecot.org/dovecot-2.0/rev/c892f3f4aae8
Anyway, time to integrate valgrind to running unit tests..
participants (2)
-
Michal Hlavinka
-
Timo Sirainen