From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: Re: test failures on 32 bit architectures.
Date: Tue, 23 Jun 2020 21:39:01 -0300 [thread overview]
Message-ID: <87o8p9nvq2.fsf@tethera.net> (raw)
In-Reply-To: <87bllar8yz.fsf@tethera.net>
David Bremner <david@tethera.net> writes:
> David Bremner <david@tethera.net> writes:
>
>> I know, I know, I don't use 32 bit architectures either. However...
>>
>> Looking at [1], it looks like there two tests consistently failing on 32
>> bit architectures (and also mips64el, FWIW).
>
> Hmm. Somewhere between when I sent this message and now, some upgrade in
> debian unstable made these failures go away for me on i386. So maybe
> I'll wait a day or so for the autobuilders to catch up, and retry the
> more exotic architectures.
I managed to duplicate the bug on the debian i386 porterbox. Here the
timestamp is 0 in the database, so if some mangling happened, it
happened during indexing.
next prev parent reply other threads:[~2020-06-24 0:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 14:18 test failures on 32 bit architectures David Bremner
2020-06-22 23:12 ` David Bremner
2020-06-24 0:39 ` David Bremner [this message]
2020-06-24 11:04 ` [PATCH] lib: avoid casting gint64 to time_t David Bremner
2020-06-24 12:40 ` David Bremner
2020-06-24 14:32 ` [PATCH 1/2] configure: detect 64 bit time_t David Bremner
2020-06-24 14:32 ` [PATCH 2/2] test: mark two tests broken on machines with 32 " David Bremner
2020-06-27 1:25 ` David Bremner
2020-06-24 19:38 ` [PATCH 1/2] configure: detect 64 " Tomi Ollila
2020-06-27 1:25 ` 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=87o8p9nvq2.fsf@tethera.net \
--to=david@tethera.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).