unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Josselin Poiret <dev@jpoiret.xyz>
To: Ricardo Wurmus <rekado@elephly.net>, guix-devel@gnu.org
Subject: Re: [core-updates] qtbase 6 ssl tests fail.
Date: Mon, 10 Apr 2023 11:40:18 +0200	[thread overview]
Message-ID: <875ya4848t.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87h6tq8cjp.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]

Hi Ricardo,

Ricardo Wurmus <rekado@elephly.net> writes:

> Hi Guix,
>
> on core-updates qtbase 6.3 fails its test suite.
>
> The tst_QSslKey group of tests has 122 failures that all look like
> this:
>
> FAIL!  : tst_QSslKey::passphraseChecks(DES) '!key.isNull()' returned FALSE. ()
>    Loc: [/tmp/guix-build-qtbase-6.3.2.drv-0/qtbase-everywhere-src-6.3.2/tests/auto/network/ssl/qsslkey/tst_qsslkey.cpp(626)]
>
> The tst_QSslKey failures are the only tests that fail.
>
> I’m currently working on upgrading linphone-desktop (I’ve upgraded all
> its dependencies already, but haven’t pushed them yet) and the current
> version needs Qt 6.
>
> Is anyone of you working on Qt 6 on core-updates?

I also got bitten by this when building my own package manifest (for
qpwgraph).  The fact that it needs quite a lot of time was quite
discouraging so I just abandoned the idea of doing it myself.  I might
revisit it by just building in a `guix shell -C` instead.

Best,
-- 
Josselin Poiret

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]

  reply	other threads:[~2023-04-10  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-08 18:13 [core-updates] qtbase 6 ssl tests fail Ricardo Wurmus
2023-04-10  9:40 ` Josselin Poiret [this message]
2023-04-10  9:49   ` Josselin Poiret
2023-04-12 20:36 ` Josselin Poiret
2023-04-12 20:38   ` [PATCH] WIP upgrade qt 6 to 6.5.0 Josselin Poiret

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=875ya4848t.fsf@jpoiret.xyz \
    --to=dev@jpoiret.xyz \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).