From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: test failures on 32 bit architectures.
Date: Mon, 22 Jun 2020 11:18:26 -0300 [thread overview]
Message-ID: <87mu4vqj4d.fsf@tethera.net> (raw)
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).
T160-json: Testing --format=json output
FAIL Search message: json, 64-bit timestamp
--- T160-json.8.expected 2020-06-22 12:29:35.053363072 +0000
+++ T160-json.8.output 2020-06-22 12:29:35.053363072 +0000
@@ -1,7 +1,7 @@
[
{
"authors": "Notmuch Test Suite",
- "date_relative": "the future",
+ "date_relative": "1970-01-01",
"matched": 1,
"query": [
"id:msg-005@notmuch-test-suite",
@@ -13,7 +13,7 @@
"unread"
],
"thread": "XXX",
- "timestamp": 32472187200,
+ "timestamp": 0,
"total": 1
}
]
T355-smime: Testing S/MIME signature verification and decryption
FAIL Verify signature on PKCS#7 SignedData message
expires: value not equal: data[0][0][0]["crypto"]["signed"]["status"][0]["expires"] = 2145914603 != 2611032858
I haven't tried to debug yet, but the first bug looks like a timestamp
overflowing 32 bits, becoming negative, and being clamped to 0.
No idea about the second.
[1]: https://buildd.debian.org/status/package.php?p=notmuch&suite=experimental
next reply other threads:[~2020-06-22 14:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 14:18 David Bremner [this message]
2020-06-22 23:12 ` test failures on 32 bit architectures David Bremner
2020-06-24 0:39 ` David Bremner
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=87mu4vqj4d.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).