From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37519@debbugs.gnu.org, "brice@waegenei.re" <brice@waegenei.re>,
37493@debbugs.gnu.org
Subject: [bug#37519] [PATCH v2 2/2] gnu: add iwd.
Date: Wed, 2 Oct 2019 00:30:21 +0200 [thread overview]
Message-ID: <20191002003021.3be21cfe@scratchpost.org> (raw)
In-Reply-To: <87sgocuazs.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]
Hi,
> > It was missing the kernel module pkcs8_key_parser, as explained in src/pkcs8.conf. Since we can't load it at build time, I disabled the test.
It's fine to do it like that in that case, but just some food for thought:
We often disable tests in cases like that because writing system tests for something like that is annoying if one has to do it manually.
Would it be possible to discover packages which need those kinds of tests (if necessary just specify an "argument" in the package record) and automatically create&run system tests for them? Guix would then run all the tests in a qemu-system container.
Something like
$ make TESTS=packages check-system
which would:
* Traverse all the packages with (#:run-tests-as-system-tests? #t)
* Automatically set up a system test to run the tests of all of these packages. Basically we could just provide guix-daemon inside a qemu guest and build the same derivation again in there, letting it load Linux kernel modules however it wants.
Especially Linux kernel-requiring (or worse, -modifying) tests are otherwise impossible to do.
Long term, I don't feel good excluding all those tests just because they are low-level.
Docs:
>there is no automatic module loading for key type parsers
Why not? Weird... there's require_module, was it not thought of--or is it inapplicable somehow?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-10-01 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <793d-5d921680-4d-485b8300@90758574>
2019-10-01 8:27 ` [bug#37493] [bug#37519] [PATCH v2 2/2] gnu: add iwd Ludovic Courtès
2019-10-01 22:30 ` Danny Milosavljevic [this message]
[not found] <73c1-5d90e780-27-4e97ad00@132980401>
2019-09-29 21:01 ` Ludovic Courtès
2019-09-26 21:44 [bug#37519] [PATCH v2 1/2] gnu: Add ell Brice Waegeneire
2019-09-26 21:44 ` [bug#37519] [PATCH v2 2/2] gnu: add iwd Brice Waegeneire
2019-09-28 20:56 ` Ludovic Courtès
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=20191002003021.3be21cfe@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=37493@debbugs.gnu.org \
--cc=37519@debbugs.gnu.org \
--cc=brice@waegenei.re \
--cc=ludo@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 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).