Am Do., 11. Mai 2023 um 22:49 Uhr schrieb David Bremner <da...@tethera.net>: > > Michael J Gruber <michaeljgruber+grubix+...@gmail.com> writes: > ... > > T350-crypto: Testing PGP/MIME signature verification and decryption ... > > PASS signature verification with signer key unavailable > > ``` > > There the suite "hangs" for about 2 minutes, followed by > > This sounds suspiciously like "timeout" kicking in and killing a test > that is taking too long. You can set NOTMUCH_TEST_TIMEOUT in the > environment to some smaller/larger number to test this.
Yes, when I set the timeout to 10m it hangs for 10min there, > The first subtest in T357 is also sending an encrypted message, so it Same after that one. I"ll attach "hang1" and "hang2" which are the process lists during those hangs. Are those subtests the only ones (or rather, the first subtests in these tests, and those tests the only ones) sending encrypted messages? > looks like some bad interaction between gpg and emacs. Maybe you can try > sending an encrypted message from emacs interactively in your chroot > environment. > > 0) you will first need to run > > gpg --no-tty --import ./test/openpgp4-secret-key.asc > > this will create a keyring etc... in the chroot > > 1) You can use the script > > ./devel/try-emacs-mua -q > > > 2) Copy the following into *scratch* and run with C-j after the last > closing paren (this is just copied from the test suite internals) > > (let ((message-send-mail-function (lambda () t)) > (mail-host-address "example.com")) > (notmuch-mua-mail) > (message-goto-to) > (insert "test_su...@notmuchmail.org\nDate: 01 Jan 2000 12:00:00 -0000") > (message-goto-subject) > (insert "My Subject") > (message-goto-body) > (insert "a body") > (mml-secure-message-encrypt) > (let ((mml-secure-smime-sign-with-sender t) > (mml-secure-openpgp-sign-with-sender t)) > (notmuch-mua-send-and-exit))) > > You will probably need to answer "c" to create the sent-mail folder at > the prompt. Thanks for these instructions. I don't get a prompt: Right after C-j, that emacs session hangs indefinitely. There was also something about "require nnheader" or something like that. "hang3" is the hanging process, which seems to be the same as for the other runs. > > At least for T350 this is strange because several subtests ran and > > passed! This indicates a race or a wrong signal trap. > > Note that those files are summaries created by test_done, so it's not > that surprising that they are not there, since test_done is not reached > in those files. I assumed the subtests would timeout separately and the test framework would catch that. If the test script itself is killed then yes, that outcome is expected :) _______________________________________________ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org