<feed xmlns='http://www.w3.org/2005/Atom'>
<title>chime/tests/test-chime-async-lifecycle.el, branch main</title>
<subtitle>Emacs chimes, notifications, and modeline reminders so you don't miss events
</subtitle>
<id>https://git.cjennings.net/chime/atom?h=main</id>
<link rel='self' href='https://git.cjennings.net/chime/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/chime/'/>
<updated>2026-07-10T00:58:27+00:00</updated>
<entry>
<title>test: add failing tests for the async generation guard and kill path</title>
<updated>2026-07-10T00:58:27+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-07-10T00:58:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/chime/commit/?id=67eb495da255d0cf00c88448f8cfd232c88563d1'/>
<id>urn:sha1:67eb495da255d0cf00c88448f8cfd232c88563d1</id>
<content type='text'>
The tests cover a fresh result being processed, a stale one discarded without touching the replacement child's handle or the failure counter, the watchdog and chime--stop both superseding the generation, and chime--kill-async-process reaping a real child and its buffer.

Where a mock can't show the behavior, the tests spawn real processes. async.el's buffer handling and the sentinel silencing are the thing under test.
</content>
</entry>
</feed>
