From: David Bremner <david@tethera.net>
To: "Dan Čermák" <dan.cermak@posteo.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Test failures with notmuch 0.32 and 0.32.1 on openSUSE
Date: Sat, 05 Jun 2021 10:50:09 -0300 [thread overview]
Message-ID: <87im2sifou.fsf@tethera.net> (raw)
In-Reply-To: <87mtspiio6.fsf@cgc-instruments.com>
Dan Čermák <dan.cermak@posteo.net> writes:
> David Bremner <david@tethera.net> writes:
>
> [snip...]
>>
>> Thanks. What about python and gnupg versions?
>
> That would be:
> Python 3.8.10
> gpg (GnuPG) 2.2.27
I installed openSUSE tumbleweed (current as of June 3) in a KVM vm, and
the tests are passing. There are some recurring issues with parallel
tests in this vm (I think some timeouts with gdb), but with
NOTMUCH_TEST_SERIALIZE=t or with no parallel in the VM, everything
passes fine both on master and 0.32.1 (from git checkouts or tarball).
The log I checked [1] _was_ running the tests in parallel.
Can you point me to a full log from a failing non-parallel test run in
tumbleweed?
Of course ideally the parallel test suite would work too, but one step
at a time.
[1]: https://build.opensuse.org/package/live_build_log/openSUSE:Factory/notmuch/standard/x86_64
\r
next prev parent reply other threads:[~2021-06-05 13:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 8:16 Test failures with notmuch 0.32 and 0.32.1 on openSUSE Dan Čermák
2021-05-19 9:05 ` Michael J Gruber
2021-05-19 11:00 ` David Bremner
2021-05-20 6:10 ` Dan Čermák
2021-05-20 9:59 ` David Bremner
2021-05-20 14:16 ` Michael J Gruber
2021-05-20 14:30 ` Dan Čermák
2021-05-20 14:46 ` Michael J Gruber
2021-05-20 15:05 ` Dan Čermák
2021-05-20 19:54 ` Tomi Ollila
2021-05-20 14:28 ` Dan Čermák
2021-06-05 13:50 ` David Bremner [this message]
2021-06-08 8:24 ` Dan Čermák
2021-06-08 13:14 ` David Bremner
2021-06-08 14:13 ` Dan Čermák
2021-06-08 14:51 ` David Bremner
2021-08-28 15:20 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87im2sifou.fsf@tethera.net \
--to=david@tethera.net \
--cc=dan.cermak@posteo.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).