From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Guix Devel <guix-devel@gnu.org>
Subject: Time travel accident
Date: Fri, 07 Apr 2023 09:47:46 +0200 [thread overview]
Message-ID: <m1o7o0gml9.fsf@fastmail.net> (raw)
Hi everyone,
For doing some experiments with Python 3.8.2, I tried to use the commit
that introduced that version into Guix;
guix time-machine --commit=ce35dc84a10b05dc891bfae03f613b907337945e \
-- shell --pure python \
-- python3
That fails, due to a build failure in OpenSSL:
building /gnu/store/nh63q12x95irxyqzls0sfalf8ih5qass-openssl-1.1.1d.drv...
| 'check' phasebuilder for `/gnu/store/nh63q12x95irxyqzls0sfalf8ih5qass-openssl-1.1.1d.drv' failed with exit code 1
build of /gnu/store/nh63q12x95irxyqzls0sfalf8ih5qass-openssl-1.1.1d.drv failed
View build log at '/var/log/guix/drvs/nh/63q12x95irxyqzls0sfalf8ih5qass-openssl-1.1.1d.drv.bz2'.
Inspecting the build log shows that the cause is a failing test:
Test Summary Report
-------------------
../test/recipes/80-test_ssl_new.t (Wstat: 256 Tests: 29 Failed: 1)
That problem has been reported elsewhere and identified as caused by an
expired certificate:
https://github.com/openssl/openssl/issues/18441
I guess there is nothing we can do retroactively to fix this, but can we
do something to prevent such issues in the future?
One idea is to allow disabling tests at the command line. I'd then run
"guix build" for that specific package with tests disabled, and
continue. That should be doable with a suitable package transformation.
Cheers,
Konrad
next reply other threads:[~2023-04-07 7:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 7:47 Konrad Hinsen [this message]
2023-04-07 8:30 ` Time travel accident Josselin Poiret
2023-04-07 10:07 ` Julien Lepiller
2023-04-07 16:10 ` Konrad Hinsen
2023-04-07 17:39 ` Julien Lepiller
2023-04-11 15:20 ` Konrad Hinsen
2023-04-12 10:17 ` Konrad Hinsen
2023-04-12 14:09 ` Simon Tournier
2023-04-13 8:14 ` Konrad Hinsen
2023-04-12 11:03 ` Simon Tournier
2023-04-12 12:53 ` Konrad Hinsen
2023-04-07 17:26 ` Simon Tournier
2023-04-17 13:32 ` Ludovic Courtès
2023-04-17 17:50 ` Simon Tournier
2023-04-17 22:16 ` Vagrant Cascadian
2023-04-18 9:39 ` Simon Tournier
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=m1o7o0gml9.fsf@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=guix-devel@gnu.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://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).