From: raingloom <raingloom@riseup.net>
To: Phil Beadling <phil@beadling.co.uk>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Getting Unit Test Results Out Of Guix Build
Date: Tue, 26 Oct 2021 06:24:29 +0200 [thread overview]
Message-ID: <20211026062429.242a504a@riseup.net> (raw)
In-Reply-To: <CAOvsyQvDjgR1PtFzwM=gRjjV=ObsL788iUVZX4FkFO_6wLbBsw@mail.gmail.com>
On Mon, 25 Oct 2021 13:30:40 +0100
Phil Beadling <phil@beadling.co.uk> wrote:
> Hi all,
>
> Given Guix builds packages in a container, is there any way of
> getting a file out of the build container for further processing?
>
> In my use case - I generate some junit test XML output during the
> build process and want to render that to a webpage rather than send
> it to stdout as part of the build process?
>
> It is possible to export the nar file using guix archive --export, and
> possible to keep failed build artifacts using -K, but there doesn't
> seem to be a way to dump out a file from a successful build?
>
> Is this against the philosphy of purely-functional builds? Obviously
> it is a side-effect to dump out an XML file, but no more so than
> sending build logs to stdout? Is it possible to dump outputs without
> breaking referential transparency on the inputs - i.e. it should be
> possible to configure a directory that is write-only for the
> container, but can be read by users outside the container?
>
> Or am I missing something obvious?
>
> Thanks,
> Phil.
Couldn't this just be another package output? Maybe not the most elegant
solution, since those are not usually used this way, but it can sort of
work. Just add a phase that copies the logs to the "tests" output if
it exists. Kinda like how the "debug" is currently used.
next prev parent reply other threads:[~2021-10-26 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 12:30 Getting Unit Test Results Out Of Guix Build Phil Beadling
2021-10-26 4:24 ` raingloom [this message]
2021-10-26 18:31 ` Phil
2021-11-04 13:52 ` Phil Beadling
2021-11-05 1:15 ` raingloom
2021-11-05 1:53 ` Phil
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=20211026062429.242a504a@riseup.net \
--to=raingloom@riseup.net \
--cc=help-guix@gnu.org \
--cc=phil@beadling.co.uk \
/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.
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).