unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Michael J Gruber <git@grubix.eu>
To: David Bremner <david@tethera.net>, Tomi Ollila <tomi.ollila@iki.fi>
Cc: notmuch@notmuchmail.org
Subject: Re: Test suite timing issues?
Date: Tue, 15 Feb 2022 16:18:06 +0100	[thread overview]
Message-ID: <164493828675.3239.10351078681225652378.git@grubix.eu> (raw)
In-Reply-To: <164491506123.3239.10549568704571641948.git@grubix.eu>

> > > BTW, I have so far run the test suite 68 times in a row without failures
> > > on a Debian s390x host. The file system is ext4, mounted relatime. It
> > > would be interesting to know what file system is yielding the failures
> > > Michael is seeing.
> 
...

> So I'll try out a bit more, and if everything else fails, then running
> the test suite with --full-scan is still better than not running it at
> all. (I would have suggested a make variable, but it's really a corner
> case. given the stat/mtime check).

Last update for now:

It's still happening sporadically only, and the archs where it does
happen use xfs (relatime,seclabel,attr2) resp. tmpfs
(nosuid,nodev,seclabel). It has to be something weird on our infra or
specifically el8.

So, either I implement `make test FULLSCAN=1` or patch in `--full-scan`
or disable the tests on epel.

Thanks for your patience :)

Cheers,
Michael

  reply	other threads:[~2022-02-15 15:21 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
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 [this message]
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=164493828675.3239.10351078681225652378.git@grubix.eu \
    --to=git@grubix.eu \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    /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).