all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: guix-devel@gnu.org
Subject: Would a Guix QA page be helpful?
Date: Sat, 06 Feb 2021 20:20:04 +0000	[thread overview]
Message-ID: <87k0rlx823.fsf@cbaines.net> (raw)

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

Hey,

The Guix Data Service has been getting better at finding problems, but
getting that data requires knowing it exists, and where to find it, and
clicking all the relevant links.

I've been wondering if it would be good to have a QA page that just
summarises and links to this information, things like:

 - Broken packages
 - Broken system tests
 - Broken fixed output package derivations
 - Lint warnings
 - ...

While I'd really like to get to a place where less packages and system
tests are unintentionally broken, and less lint warnings are
unintentionally introduced, at the moment, there are plenty of these
problems. There's also things like the broken package sources, where
there will probably always be new breakages being introduced.

Given the Guix Data Service can look at what's changed within a time
period on a branch, recent breakages could also be displayed.

This could potentially sit at qa.guix.gnu.org.

Any thoughts?

Thanks,

Chris

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

             reply	other threads:[~2021-02-06 20:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06 20:20 Christopher Baines [this message]
2021-02-06 21:02 ` Would a Guix QA page be helpful? Léo Le Bouter
2021-02-06 21:52 ` Ludovic Courtès
2021-02-07 21:13 ` Bengt Richter
2021-02-08  0:26   ` zimoun
2021-02-07 22:41 ` Björn Höfling
2021-02-08  0:28 ` zimoun

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k0rlx823.fsf@cbaines.net \
    --to=mail@cbaines.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.