<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/T210-raw.sh, branch master</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=master</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2022-07-30T11:39:13Z</updated>
<entry>
<title>CLI/show: initial support for --duplicate for (raw output only)</title>
<updated>2022-07-30T11:39:13Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2022-07-01T21:45:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=cef5eaaef61b1f4dde6276ef267fb923f1b16680'/>
<id>urn:sha1:cef5eaaef61b1f4dde6276ef267fb923f1b16680</id>
<content type='text'>
Add command line argument --duplicate, analogous with that already
supported for notmuch-search.

Use of a seperate function for _get_filename is mainly a form of
documentation at this point.

md5sum is of course a weak hash, but it is good enough for
this (non-adversarial) test suite use.
</content>
</entry>
<entry>
<title>test: clean up some extra whitespace.</title>
<updated>2021-03-12T11:19:14Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-01-16T01:29:17Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=97fadd0645e908ff8322577a983dc710bfda33d6'/>
<id>urn:sha1:97fadd0645e908ff8322577a983dc710bfda33d6</id>
<content type='text'>
The extra space is mainly just untidy.
</content>
</entry>
<entry>
<title>test: fix python 3.8.4 related regression in T210-raw</title>
<updated>2020-07-03T10:23:32Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-07-03T10:23:32Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e9f8ffd882aba446ee27a9c32bb1e1475512d3f7'/>
<id>urn:sha1:e9f8ffd882aba446ee27a9c32bb1e1475512d3f7</id>
<content type='text'>
It seems (at least in 3.8.4~rc1-1 on Debian) that set_content requires
at least one line.
</content>
</entry>
<entry>
<title>cli/show: avoid empty write to stdout in format_part_raw</title>
<updated>2019-05-05T11:01:17Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-05-04T22:29:08Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ae6b52488d71b879e2eb05d5ca6c4d4f641d0558'/>
<id>urn:sha1:ae6b52488d71b879e2eb05d5ca6c4d4f641d0558</id>
<content type='text'>
Previously if the input was exactly a multiple of the internal buffer
size, notmuch would attempt to fwrite nothing to stdout, but still
expected fwrite to return 1, causing a failure that looked like this:

  $ notmuch show --format=raw id:87o96f1cya.fsf@codeaurora.org
    ...entire message shown as expected..
  Error: Write failed
  $ echo $?
  1

To fix the problem don't call fwrite at all when there's nothing to
write.

Amended by db: add some tests of message sizes likely to cause this
problem.
</content>
</entry>
<entry>
<title>test: use $(dirname "$0") for sourcing test-lib.sh</title>
<updated>2017-10-20T22:52:49Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-09-25T20:38:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a863de1e43ee34f6f5794a2759fdceb287e851aa'/>
<id>urn:sha1:a863de1e43ee34f6f5794a2759fdceb287e851aa</id>
<content type='text'>
Don't assume the tests are always run from within the source tree.
</content>
</entry>
<entry>
<title>cli: tell how many messages were precisely matched when expected 1 match</title>
<updated>2016-05-19T10:49:03Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2016-05-07T19:24:18Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=eac29763896e457a738f811b2c2ba8f877498e62'/>
<id>urn:sha1:eac29763896e457a738f811b2c2ba8f877498e62</id>
<content type='text'>
In case of notmuch reply and notmuch show --part=N it is required that
search terms match to one message. If match count was != 1, error
message "Error: search term did not match precisely one message"
was too vague to explain what happened.

By appending (matched &lt;num&gt; messages) to the error message it
makes the problem more understandable (e.g when &lt;num&gt; is '0'
user reckons the query had a typo in it).
</content>
</entry>
<entry>
<title>test: make script exit (1) if it "fails" to source (.) a file</title>
<updated>2015-08-07T19:56:39Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2015-08-06T09:13:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=02a2eeb427d6b424029f6e5e5ddad4c6ec987741'/>
<id>urn:sha1:02a2eeb427d6b424029f6e5e5ddad4c6ec987741</id>
<content type='text'>
The files (test) scripts source (with builtin command `.`) provides
information which the scripts depend, and without the `source` to
succeed allowing script to continue may lead to dangerous situations
(e.g. rm -rf "${undefined_variable}"/*).

At the end of all source (.) lines construct ' || exit 1' was added;
In our case the script script will exit if it cannot find (or read) the
file to be sourced. Additionally script would also exits if the last
command of the sourced file exited nonzero.
</content>
</entry>
<entry>
<title>test: renamed test scripts to format T\d\d\d-name.sh</title>
<updated>2014-01-13T18:16:46Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2014-01-09T15:18:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a755c9d6a9099366cc82ba3a4bee8e6d2b83d529'/>
<id>urn:sha1:a755c9d6a9099366cc82ba3a4bee8e6d2b83d529</id>
<content type='text'>
All test scripts to be executed are now named as T\d\d\d-name.sh,
numers in increments of 10.

This eases adding new tests and developers to see which are test scripts
that are executed by test suite and in which order.
</content>
</entry>
</feed>
