thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.10_rc1 2011-11-13T13:44:36Z 2011-11-13T13:44:36Z Dmitry Kurochkin dmitry.kurochkin@gmail.com 2011-07-01T02:23:48Z urn:sha1:5964a760a5d26f94ea1c262a25f80725877e3445 Do not redirect test_emacs stderr to /dev/null. Test_emacs uses emacsclient(1) now and it does not print unwanted messages (like those from `message') to stderr. But it does print useful errors, e.g. when emacs server connection fails, given expression is not valid or undefined function is called. 2011-11-13T03:21:44Z Tomi Ollila tomi.ollila@iki.fi 2011-11-10T23:43:03Z urn:sha1:085d45e3891a7def705082c21fc112a97d85062e In the last line of run_emacs, exec the emacs process. With one fork less the process list is (also) neater. 2011-11-11T23:24:53Z Tomi Ollila tomi.ollila@iki.fi 2011-11-11T21:33:58Z urn:sha1:2f2ea8a49a9e56a1d7d8cfad8d2d109070b04bf7 dtach is simpler than screen and is not setuid/setgid program so TMPDIR does not get cleared by dynamic loader when executed 2011-11-06T00:54:40Z Dmitry Kurochkin dmitry.kurochkin@gmail.com 2011-07-01T04:55:17Z urn:sha1:746a13e6f40431ffa931ef51834ac0eb794ee554 Set SCREENRC and SYSSCREENRC environment variables to "/dev/null" as suggested by Jim Paris to avoid potential problems with screen(1) configuration files. 2011-11-05T23:49:27Z Dmitry Kurochkin dmitry.kurochkin@gmail.com 2011-07-01T04:55:16Z urn:sha1:a1ea4e914f5392a07ede2e6fc5f4350368e267b1 Before the change, emacs run in daemon mode without any visible buffers. Turns out that this affects emacs behavior in some cases. In particular, `window-end' function returns `point-max' instead of the last visible position. That makes it hard or impossible to implement some tests. The patch runs emacs in a detached screen(1) session. So that it works exactly as if it has a visible window. Note: screen terminates when emacs exits. So the patch does not introduce new "running processes left behind" issues. 2011-10-22T22:43:02Z David Bremner bremner@debian.org 2011-10-19T20:51:24Z urn:sha1:f4148e9d21f391ecd2a2100588adb55d471dac18 - explain test_expect_equal_file - remove mention of test_expect_failure, since that function was removed. Based on id:"1317317811-29540-1-git-send-email-thomas@schwinge.name" 2011-09-13T02:36:00Z Austin Clements amdragon@mit.edu 2011-05-12T13:11:36Z urn:sha1:003e718020b335f329f852ff1a3da23873d2ff6e This makes test_expect_* return non-zero if the test fails, so the caller can make decisions based on this, such as setting test prerequisites. 2011-09-13T02:35:59Z Austin Clements amdragon@mit.edu 2011-05-12T13:09:06Z urn:sha1:5ae1b9c328518a3b09be827ee59498b0598119ff For these types of tests, the test name is previously recorded in a variable, not passed to the test function, so pass this variable to test_skip. 2011-09-13T02:35:21Z David Bremner bremner@debian.org 2011-09-13T01:40:57Z urn:sha1:22af786838793ed97fa3dbb1d223e90602912b71 This means that test_subtest_known_broken needs to be called before every known broken subtest, which is no different than what is documented for the test_begin_subtest case. The assumption is that every test ends up calling either skipping, calling test_ok_ or test_failure_ and and the latter in turn delegate to the known_broken versions in the case where test_subtest_known_broken_ is set. 2011-09-10T13:13:27Z Dmitry Kurochkin dmitry.kurochkin@gmail.com 2011-07-04T04:07:20Z urn:sha1:4cc67276885990c38bc2bcc79eedbb0851e2bc8a There is existing support for broken tests. But it is not convenient to use. The primary issue is that we have to maintain a set of test_expect_*_failure functions which are equivalent to the normal test_expect_* counterparts except for what functions are called for result reporting. The patch adds test_subtest_known_broken function which marks a subset as broken, making the normal test_expect_* functions behave as test_expect_*_failure. All test_expect_*_failure functions are removed. Test_known_broken_failure_ is changed to format details the same way as test_failure_ does. Another benefit of this change is that the diff when a broken test is fixed would be small and nice. Documentation is updated accordingly.