<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/test-lib.sh, branch 0.34.2</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.34.2</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.34.2'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2021-12-04T12:36:23Z</updated>
<entry>
<title>test: add python-cffi bindings to path for test_python</title>
<updated>2021-12-04T12:36:23Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-10-30T16:22:33Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5f077bef37462267258f95f7400596a157878b14'/>
<id>urn:sha1:5f077bef37462267258f95f7400596a157878b14</id>
<content type='text'>
This will allow testing the new python bindings using test_python, in
addition to the current invocation of pytest.
</content>
</entry>
<entry>
<title>test/T355-smime: Use key as exported by gpgsm</title>
<updated>2021-09-29T23:04:31Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-09-28T01:30:08Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4760b4470c5d5782e52bd1a7761d9975a1db1fec'/>
<id>urn:sha1:4760b4470c5d5782e52bd1a7761d9975a1db1fec</id>
<content type='text'>
As reported in id:87h7pxiek3.fsf@tethera.net, the previous version of
the test is flaky. There is some so-far undebugged interaction between
openssl and gpgsm that causes the keys to fail to import. As a
potential workaround, use the key as exported by gpgsm, and eliminate
openssl from this particular pipeline.
</content>
</entry>
<entry>
<title>test: add test_expect_equal_file_nonempty</title>
<updated>2021-08-21T21:55:41Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-08-04T10:42:32Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=474a7f8e6506ed5c027a5f8e4c11261cda5a17dc'/>
<id>urn:sha1:474a7f8e6506ed5c027a5f8e4c11261cda5a17dc</id>
<content type='text'>
A common bug in tests is that the code used to generate the EXPECTED
file fails, generating no output. When the code generating the OUTPUT
file fails in the same way, the test passes, even though there is a
failure being hidden. Add a new test function that guards against
this.
</content>
</entry>
<entry>
<title>test: factor out test_diff_file_</title>
<updated>2021-08-21T21:55:27Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-08-04T10:42:31Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=78045301e7dd3caf82d5efc241d10b351be33b28'/>
<id>urn:sha1:78045301e7dd3caf82d5efc241d10b351be33b28</id>
<content type='text'>
A following commit will use this new function in a public test
function.
</content>
</entry>
<entry>
<title>test/expect_equal_file: whitespace cleanup</title>
<updated>2021-08-21T21:51:04Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-08-04T10:42:30Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f2e6f311c7b4bf4c459c7e73c8a8d3fe157851c4'/>
<id>urn:sha1:f2e6f311c7b4bf4c459c7e73c8a8d3fe157851c4</id>
<content type='text'>
No functional change, just reindent to Emacs defaults.
</content>
</entry>
<entry>
<title>test: revert to mkdir -p to make results directory.</title>
<updated>2021-08-03T23:35:13Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-08-03T23:35:13Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3fc2e5f23bbbe3e9341397712a6a4d786adb8d6a'/>
<id>urn:sha1:3fc2e5f23bbbe3e9341397712a6a4d786adb8d6a</id>
<content type='text'>
As suggested by id:m21r7al3mt.fsf@guru.guru-group.fi
</content>
</entry>
<entry>
<title>cli/show: produce "email" element in sigstatus</title>
<updated>2021-06-26T16:07:47Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2021-05-27T01:44:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8c29a5da096b0314c6cca8889b740b79a9a548ed'/>
<id>urn:sha1:8c29a5da096b0314c6cca8889b740b79a9a548ed</id>
<content type='text'>
When the certificate that signs a message is known to be valid, GMime
is capable of reporting on the e-mail address embedded in the
certificate.

We pass this information along to the caller of "notmuch show", as
often only the e-mail address of the certificate has actually been
checked/verified.

Furthermore, signature verification should probably at some point
compare the e-mail address of the caller against the sender address of
the message itself.  Having to parse what gmime thinks is a "userid"
to extract an e-mail address seems clunky and unnecessary if gmime
already thinks it knows what the e-mail address is.

See id:878s41ax6t.fsf@fifthhorseman.net for more motivation and discussion.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>Merge branch 'release'</title>
<updated>2021-06-20T20:15:20Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-06-20T20:15:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8dbd5deb8d3bbfda9554163c8d4cb2474c505c87'/>
<id>urn:sha1:8dbd5deb8d3bbfda9554163c8d4cb2474c505c87</id>
<content type='text'>
</content>
</entry>
<entry>
<title>test: check openssl prequisite for add_gpgsm_home</title>
<updated>2021-06-08T20:15:46Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-06-08T19:39:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a19d2b0d2b8c666d0a3641dc2e7e1b4e73b7c2bd'/>
<id>urn:sha1:a19d2b0d2b8c666d0a3641dc2e7e1b4e73b7c2bd</id>
<content type='text'>
This is a fix for the test failures reported by Dan Čermák [1].

It is more robust to check for the prerequisite inside the function
that uses it, rather than in every test file that calls the function.

[1]: id:87k0n4fqgm.fsf@tethera.net
</content>
</entry>
<entry>
<title>test: aggregate-results updates</title>
<updated>2021-06-07T23:16:33Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2021-05-17T08:11:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6f0f83660e222cfdd05b05ad134763a7ab26f097'/>
<id>urn:sha1:6f0f83660e222cfdd05b05ad134763a7ab26f097</id>
<content type='text'>
notmuch-test will now call aggregate-results.sh with file list
that it compiles based on the test ran, and aggregate-results
will report failure is any of the test files are missing.

With this notmuch-test no longer has to exit in non-parallel
run if some test fail to write its report file -- so it works
as parallel tests in this sense.

Changed test_done() in test-lib.sh write report file in one write(2),
so there is (even) less chance it being partially written. Also,
now it writes 'total' last and aggregate-results.sh expects this
line to exist in all report files for reporting to be successful.

Added 'set -eu' to notmuch-test and modified code to work with
these settings. That makes it harder to get mistakes slipped
into committed code.
</content>
</entry>
</feed>
