From: Michael J Gruber <git@grubix.eu>
To: Notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: Test suite timing issues?
Date: Fri, 11 Feb 2022 15:04:14 +0100 [thread overview]
Message-ID: <164458825459.3086.13267317086536749487.git@grubix.eu> (raw)
In-Reply-To: <164458773197.3086.16103597141743611268.git@grubix.eu>
Michael J Gruber venit, vidit, dixit 2022-02-11 14:55:32:
> Hi there,
>
> I'm trying to package notmuch for Redhat's enterprise linux and clones
> (EPEL, extra packages for enterprise linux).
>
> This looks mostly fine, including the tests, except for intermittent
> failures on epel-8-s390x. They look like the below, or in tests
> following those, and apparantly all have to do with "db not synced yet"
> or such, so that a message one subtest creates only shows up in the db
> for the next subtest.
>
> I've also had completely fine test runs on epel-8-s390x, but I'm
> starting to wonder whether I've just been lucky so far on other
> platforms ... Could it be possible that generate_message(), even though
> adding the message, still returns false and therefore add_message() does
> not call "notmuch new"? One might want to drop the "&&" there in
> test-lib-common, I dunno. This shouldn't be "intermittent".
>
> Michael
>
> T210-raw: Testing notmuch show --format=raw
> FAIL Attempt to show multiple raw messages
> --- T210-raw.1.expected 2022-02-11 13:22:28.011556841 +0000
> +++ T210-raw.1.output 2022-02-11 13:22:28.011556841 +0000
> @@ -1 +1,7 @@
> -Error: search term did not match precisely one message (matched 2 messages).
> +From: Notmuch Test Suite <test_suite@notmuchmail.org>
> +To: Notmuch Test Suite <test_suite@notmuchmail.org>
> +Message-Id: <msg-001@notmuch-test-suite>
> +Subject: Test message #1
> +Date: Fri, 05 Jan 2001 15:43:56 +0000
> +
> +This is just a test message (#1)
> PASS Show a raw message
> FAIL Show another raw message
> --- T210-raw.3.expected 2022-02-11 13:22:28.031556841 +0000
> +++ T210-raw.3.output 2022-02-11 13:22:28.031556841 +0000
> @@ -1,7 +1 @@
> -From: Notmuch Test Suite <test_suite@notmuchmail.org>
> -To: Notmuch Test Suite <test_suite@notmuchmail.org>
> -Message-Id: <msg-002@notmuch-test-suite>
> -Subject: Test message #2
> -Date: GENERATED_DATE
>
> -This is just a test message (#2)
> Error: search term did not match precisely one message (matched 0 messages).
Similar apparent timing issue on epel-8-aarch64:
FAIL Adding message with long ID
--- T290-long-id.2.expected 2022-02-11 13:55:17.028415326 +0000
+++ T290-long-id.2.output 2022-02-11 13:55:17.028415326 +0000
@@ -1 +1 @@
-Added 1 new message to the database.
+No new mail.
FAIL Referencing long ID after adding
--- T290-long-id.3.expected 2022-02-11 13:55:17.078415753 +0000
+++ T290-long-id.3.output 2022-02-11 13:55:17.078415753 +0000
@@ -1 +1 @@
-Added 1 new message to the database.
+Added 2 new messages to the database.
Note how that message from the 1st subtest shows up only in the second.
next prev parent reply other threads:[~2022-02-11 14:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 13:55 Test suite timing issues? Michael J Gruber
2022-02-11 14:04 ` Michael J Gruber [this message]
2022-02-12 0:03 ` David Bremner
2022-02-12 13:32 ` Michael J Gruber
2022-02-12 14:30 ` David Bremner
2022-02-12 15:06 ` Tomi Ollila
2022-02-12 15:29 ` David Bremner
2022-02-12 19:40 ` David Bremner
2022-02-12 20:45 ` Tomi Ollila
2022-02-12 20:54 ` Michael J Gruber
2022-02-12 21:09 ` David Bremner
2022-02-12 21:53 ` Michael J Gruber
2022-02-12 22:14 ` Tomi Ollila
2022-02-13 8:29 ` Tomi Ollila
2022-02-14 14:01 ` David Bremner
2022-02-14 14:48 ` Tomi Ollila
2022-02-14 22:53 ` Tomi Ollila
2022-02-15 8:51 ` Michael J Gruber
2022-02-15 15:18 ` Michael J Gruber
2022-02-16 9:52 ` [PATCH] test: allow to use --full-sync Michael J Gruber
2022-02-16 13:04 ` David Bremner
2022-02-16 15:53 ` Michael J Gruber
2022-02-16 21:17 ` Tomi Ollila
2022-02-16 22:01 ` Tomi Ollila
2022-02-17 12:26 ` 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=164458825459.3086.13267317086536749487.git@grubix.eu \
--to=git@grubix.eu \
--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).