From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>, 56137-done@debbugs.gnu.org
Cc: phodina <phodina@protonmail.com>
Subject: bug#56137: OpenSSL 3.0.3/1.1.1n includes a time-dependent test
Date: Wed, 22 Jun 2022 12:49:51 +0200 [thread overview]
Message-ID: <80d9565a7af986075ecc93bc64ce6a48d1381efc.camel@telenet.be> (raw)
In-Reply-To: <87ilot3ru7.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Ludovic Courtès schreef op wo 22-06-2022 om 12:39 [+0200]:
> That commit skips the test. I tried another approach with ‘datefudge’,
> which has the advantage of being more explicit and future-proof (should
> there be similar issues lying around):
>
> (invoke "datefudge" "2022-01-01"
> "make" test-target
> #$@(if (or (target-arm?) (target-riscv64?))
> #~("TESTS=-test_afalg")
> #~()))
Looking at <https://github.com/openssl/openssl/issues/15179>,
upsteam just replaces the certificates when these things happen, so
there could easily be more time bombs. As such, WDYT of removing _all_
the certs in tests/certs for robustness, maybe generating them locally
with test/smime-certs/mksmime-certs.sh?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-22 11:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 9:58 bug#56137: OpenSSL 3.0.3/1.1.1n includes a time-dependent test Ludovic Courtès
2022-06-22 10:39 ` Ludovic Courtès
2022-06-22 10:49 ` Maxime Devos [this message]
2022-06-24 14:47 ` Ludovic Courtès
2022-06-24 15:00 ` Maxime Devos
2023-02-26 5:29 ` bug#56137: [PATCH 1/2] gnu: openssl-1.1: Do not quasiquote arguments Maxim Cournoyer
2023-02-26 5:29 ` bug#56137: [PATCH 2/2] gnu: openssl-1.1: Run the test suite through datefudge Maxim Cournoyer
2023-02-26 6:03 ` Maxim Cournoyer
2023-02-27 4:03 ` bug#56137: bug#58650: OpenSSL 1.1.1n test failures due to expired certificates (time bomb) Maxim Cournoyer
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80d9565a7af986075ecc93bc64ce6a48d1381efc.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=56137-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=phodina@protonmail.com \
/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://git.savannah.gnu.org/cgit/guix.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).