all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 75277@debbugs.gnu.org
Subject: [bug#75277] [PATCH v4 1/2] tests: Add tests for all the longterm-support kernels.
Date: Fri,  3 Jan 2025 14:44:03 -0500	[thread overview]
Message-ID: <a1b1558d32b225aca6084d8eeb86272caf8d5447.1735933443.git.leo@famulari.name> (raw)
In-Reply-To: <cover.1735796720.git.leo@famulari.name>

* gnu/tests/base.scm (%test-linux-libre-6.6, %test-linux-libre-6.1): New tests.

Change-Id: Ica31ae263348c38ac21efeb65d9a245e1a877268
---
 gnu/tests/base.scm | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/gnu/tests/base.scm b/gnu/tests/base.scm
index 9430cbee12..95a962ae97 100644
--- a/gnu/tests/base.scm
+++ b/gnu/tests/base.scm
@@ -577,6 +577,12 @@ (define %test-basic-os
   (test-basic-os))
 
 ;; Ensure the LTS kernels are up to snuff, too.
+(define %test-linux-libre-6.6
+  (test-basic-os linux-libre-6.6))
+
+(define %test-linux-libre-6.1
+  (test-basic-os linux-libre-6.1))
+
 (define %test-linux-libre-5.15
   (test-basic-os linux-libre-5.15))
 

base-commit: f1669d5cd8a52a1e034e46451787db396aa530ec
-- 
2.46.0





  parent reply	other threads:[~2025-01-03 19:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02  5:45 [bug#75277] [PATCH 0/1] Linux-libre 6.12 WIP Leo Famulari
2025-01-02  5:45 ` [bug#75278] [PATCH 1/1] gnu: Add linux-libre-6.12 Leo Famulari
2025-01-02  6:00   ` [bug#75278] Oops Leo Famulari
2025-01-02  5:58 ` [bug#75277] [PATCH] gnu: Add linux-libre-6.12 Leo Famulari
2025-01-02 18:21 ` Dariqq
2025-01-02 19:02   ` Leo Famulari
2025-01-02 19:04 ` [bug#75277] [PATCH v2] " Leo Famulari
2025-01-02 22:30 ` [bug#75277] [PATCH v3] " Leo Famulari
2025-01-03 19:44 ` Leo Famulari [this message]
2025-01-03 19:44   ` [bug#75277] [PATCH v4 2/2] " Leo Famulari
2025-01-07 23:15 ` bug#75277: " Leo Famulari

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=a1b1558d32b225aca6084d8eeb86272caf8d5447.1735933443.git.leo@famulari.name \
    --to=leo@famulari.name \
    --cc=75277@debbugs.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.