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: Andreas Enge <andreas@enge.fr>
Cc: 69068@debbugs.gnu.org
Subject: [bug#69068] To test or not to test?
Date: Wed, 28 Feb 2024 13:47:47 +0200	[thread overview]
Message-ID: <rfu3i6umq422ybbmi6h7ggyeqptor3beun3rbnvdxcsmzq22tv@ein4ptojvip7> (raw)
In-Reply-To: <Zd8Ly3Yp0JPNW_uL@jurong>

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

On Wed, Feb 28, 2024 at 11:32:43AM +0100, Andreas Enge wrote:
> Hello,
> 
> I also looked at this just now and am confused by the test situation.
> Should one not either disable tests altogether, or just comment out
> some of them?

I don't believe any of them even compile with Qt6. The test suite has
been unmaintained for years, so it doesn't really tell anything about
whether the program works correctly or not.

I would certainly agree that it is better to remove just the failing
ones if the issues were actual test failures due to how Guix packaging
works. Here the problem is that the project effectively no longer has a
test suite.

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

  reply	other threads:[~2024-02-28 11:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12  7:03 [bug#69068] [PATCH] gnu: kitsas: Update to 5.4.1 Saku Laesvuori via Guix-patches via
2024-02-13 11:30 ` Christopher Baines
2024-02-13 12:17   ` Saku Laesvuori via Guix-patches via
2024-02-28 10:32 ` [bug#69068] To test or not to test? Andreas Enge
2024-02-28 11:47   ` Saku Laesvuori via Guix-patches via [this message]
2024-02-28 12:36     ` Andreas Enge
2024-02-28 12:49       ` Andreas Enge
2024-02-28 15:36         ` bug#69068: " 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=rfu3i6umq422ybbmi6h7ggyeqptor3beun3rbnvdxcsmzq22tv@ein4ptojvip7 \
    --to=guix-patches@gnu.org \
    --cc=69068@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --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).