thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.6_254 2011-06-23T10:05:25Z 2011-06-23T10:05:25Z David Bremner bremner@debian.org 2011-06-22T11:58:01Z urn:sha1:fba968dbfa806dc517fc55d1f28cf208f0316863 The worry here is that a binary linking with libnotmuch might lose access to Xapian::Error symbols because libnotmuch hides them. We are careful here to create ./fakedb/.notmuch in order to trigger a Xapian exception, and not just a missing file check. Thanks to jrollins and amddragon for suggestions. (cherry picked from commit 66f37f5f6864a988f94ddb893e3a176af57f6c8e) 2011-06-22T13:38:33Z Carl Worth cworth@cworth.org 2011-06-21T21:54:10Z urn:sha1:b0ba84f9e71b0f117dc0bdf0b790c6e2341d3949 The main() function should be written as just another function with a return value. This allows for more reliable code reuse. Imagine that main() grows too large and needs to be factored into multiple functions. At that point, exit() is probably the wrong thing, yet can also be hard to notice as it's in less-frequently-tested exceptional cases. 2011-06-22T13:38:33Z Dmitry Kurochkin dmitry.kurochkin@gmail.com 2011-06-16T10:32:08Z urn:sha1:41a094624a079f4a145aba37e8059f8774dfaec6 * Remove unused variables in main(): buf, bytes and greeting. * Replace return with no value in main() with exit(3). 2011-06-22T11:11:32Z David Bremner bremner@debian.org 2011-05-28T09:50:11Z urn:sha1:114eb1c52095487caed1de8746f2741da7a3ead1 Each top level test (basic, corpus, etc...) is run with a fixed timeout of 2 minutes. The goal here is to treat a hung test as a failure. The emacs test for sending mail is known to be problematic on the Debian autobuilders. This is both a bandaid fix for that, and a sensible long term feature. (cherry picked from commit 5f99c80e02736c90495558d9b88008a768876b29) 2011-06-15T14:07:32Z Dmitry Kurochkin dmitry.kurochkin@gmail.com 2011-05-26T21:38:34Z urn:sha1:59b251ef940609dac7e17528065a39544463e0b4 This test is expected to fail as it exposes a current bug, (which we hope to fix soon). 2011-06-11T00:20:22Z Carl Worth cworth@cworth.org 2011-06-11T00:18:27Z urn:sha1:b7db7ea42056b96578b329db5a184c9c408062c2 The intent was always to make these Received headers span multiple lines. But the escapes were causing the shell to ignore the newlines, so that the result instead was long Received headers on a single line each. Fixing the intent here doesn't actually change the test-suite results at all. 2011-06-11T00:03:14Z Carl Worth cworth@cworth.org 2011-06-10T23:53:45Z urn:sha1:ac43a96988091d1ac7356e618b496ff8eef5a31c This is much more realistic, as most messages in the wild will have multiple Received headers. Also, this demonstrates a current bug in the Received header parsing, (multiple Received headers are not properly concatenated depending on the order in which headers are parsed in a message). 2011-06-10T23:28:26Z Carl Worth cworth@cworth.org 2011-06-10T23:28:26Z urn:sha1:d5edb1122db86dadd0d98dd8ccf3431e4d021337 This tests the recently-added detection/hiding of top-posted quotations and in the testing, it takes advantage of the less-recently-added visible-buffer-string function for emitting only the visible text from a buffer. 2011-06-03T22:24:35Z Jameson Graef Rollins jrollins@finestructure.net 2011-05-28T21:16:30Z urn:sha1:61ff61cc2cb12ecc5020477bf8f7c1b4d31f953a Again, this is a much cleaner and more thorough test, and in fact exposes a bug in the format=text output, that will be fixed the next commit. Because of this, some of the multipart tests currently fail. 2011-06-03T21:29:05Z Jameson Graef Rollins jrollins@finestructure.net 2011-05-28T20:46:24Z urn:sha1:5b0bf70faa57651993b5e80a3a25467c12e5f9cf This is a much cleaner way to do the emacs tests, since we're actually comparing output against existing files with expected output. We also won't miss any trailing newlines this way. And speaking of which, one of the expected output files was actually missing a trailing blank line that was actually in one of the original messages, so this was fixed.