unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: KDE in core-updates
Date: Sat, 25 Feb 2023 19:19:15 +0100	[thread overview]
Message-ID: <878rglwqu4.fsf@gnu.org> (raw)
In-Reply-To: <Y/iSyptIaTpfQwR8@jurong> (Andreas Enge's message of "Fri, 24 Feb 2023 11:34:50 +0100")

Hi,

Andreas Enge <andreas@enge.fr> skribis:

> And another undebuggable (?) failure, this time for qtbase:
>
> Total Test time (real) = 544.95 sec
>
> The following tests FAILED:
> 	354 - tst_qsslkey (Failed)
> Errors while running CTest

CTest produces log files for test suites.  I forgot the exact file name
but it should be findable in the build tree with a ‘--keep-failed’
build.

That doesn’t mean it’ll be easy of course.  :-)

Given the test name, one would hope that it’s the usual time bomb of an
expired X.509 certificate.

Ludo’.


  reply	other threads:[~2023-02-25 18:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 13:59 KDE in core-updates Andreas Enge
2023-02-24 10:34 ` Andreas Enge
2023-02-25 18:19   ` Ludovic Courtès [this message]
2023-02-26 12:44     ` Qt in core-updates (was: KDE in core-updates) Andreas Enge
2023-02-26 23:43       ` Philip McGrath
2023-02-27  2:38         ` kiasoc5
2023-02-27 19:02           ` Efraim Flashner
2023-02-28 15:13             ` Andreas Enge
2023-02-28 17:59               ` Qt in core-updates Andreas Enge
2023-02-28 18:09               ` Andreas Enge
2023-02-28 18:20                 ` Leo Famulari
2023-02-28 20:51                   ` Andreas Enge
2023-02-28 20:55                     ` Andreas Enge
2023-02-28 23:54                       ` Andreas Enge
2023-03-01  0:05                         ` Andreas Enge
2023-03-15 13:53 ` KDE " Andreas Enge

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=878rglwqu4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --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).