Quoth Jameson Graef Rollins on Aug 01 at  8:10 pm:
> On Wed, Aug 01 2012, David Bremner <david@tethera.net> wrote:
> > As I mentioned on IRC, the test only fails on the Debian build machines
> > (building in a clean chroot using sbuild is not enough) so it isn't
> > really clear how to duplicate the it. Perhaps building in a clean
> > virtual machine without networking would do it.  For which tests fail,
> > see
> >
> > https://buildd.debian.org/status/fetch.php?pkg=notmuch&arch=i386&ver=0.13.2-1&stamp=1338740444
> >
> > I think the first things to fail are emacs tests. At a wild guess, it
> > looks like all of the failing tests are related to emacs.
> 
> From a cursory look that does appear to be the case.  The non-emacs
> tests that are also failing (json and crypto) are using
> emacs_deliver_message.  Do we have any idea what's going on here?

There is one other illuminating tidbit in the buildd log:

emacs-subject-to-filename: Testing emacs: mail subject to filename
test-lib.sh: line 187: 30606 Terminated              sleep 1
FATAL: Unexpected exit with code 1

>From a cursory glance, emacs-subject-to-filename appears to be the
only test that calls test_emacs outside of a subtest and hence without
stdout/stderr redirection.

The line number is useless, but, assuming valgrind isn't enabled,
there's only one place we sleep 1 in test-lib.sh: in the loop in
test_emacs that waits for the Emacs server to start up.  Furthermore,
timeout sends SIGTERM by default, suggesting that we're timing out
while we're spinning in that loop.