[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Getting Unit Test Results Out Of Guix Build
From: |
raingloom |
Subject: |
Re: Getting Unit Test Results Out Of Guix Build |
Date: |
Tue, 26 Oct 2021 06:24:29 +0200 |
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.