unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Saku Laesvuori via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 62292-done@debbugs.gnu.org, mirai@makinata.eu
Subject: [bug#62292] [PATCH] gnu: Add kitsas
Date: Thu, 20 Apr 2023 14:38:12 +0300	[thread overview]
Message-ID: <20230420113812.np2jslq2dv4muqs6@X-kone> (raw)
In-Reply-To: <87cz3yvoa1.fsf@gnu.org>

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

> >> The test failures are worrisome though.  Could you investigate why those
> >> tests are failing or crashing?
> >> 
> >> Those failures may indicate real issues.  Or it could be that they
> >> require a running X server (other packages usually solve that by
> >> spawning ‘Xvfb’ right before the ‘check’ phase).
> >
> > The tests also fail on an Arch linux machine with a running X server. I
> > tried removing the failing ones, but that caused some of the previously
> > passing ones to start segfaulting, so I have no idea how to fix them
> > properly.
> 
> OK.  Could you report it upstream?

I'll send the maintainer an email as their issue tracker is on Github
and I'd prefer not registering an account there.

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

  reply	other threads:[~2023-04-20 11:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 10:56 [bug#62292] [PATCH] gnu: Add kitsas Saku Laesvuori via Guix-patches via
2023-03-20 18:09 ` Bruno Victal
2023-03-22 12:54 ` [bug#62292] [PATCH v2] " Saku Laesvuori via Guix-patches via
2023-04-17 21:29   ` bug#62292: [PATCH] " Ludovic Courtès
2023-04-18 14:51     ` [bug#62292] " Saku Laesvuori via Guix-patches via
2023-04-20 10:30       ` Ludovic Courtès
2023-04-20 11:38         ` Saku Laesvuori via Guix-patches via [this message]
2023-04-20 12:37           ` Saku Laesvuori via Guix-patches via

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=20230420113812.np2jslq2dv4muqs6@X-kone \
    --to=guix-patches@gnu.org \
    --cc=62292-done@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mirai@makinata.eu \
    --cc=saku@laesvuori.fi \
    /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).