From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id iB0mKo9BeGESqgAAgWs5BA (envelope-from ) for ; Tue, 26 Oct 2021 19:57:35 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id 6LS6JY9BeGHoPQAAbx9fmQ (envelope-from ) for ; Tue, 26 Oct 2021 17:57:35 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 7FDEEAC84 for ; Tue, 26 Oct 2021 19:57:34 +0200 (CEST) Received: from localhost ([::1]:36964 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mfQhY-0004Po-J8 for larch@yhetil.org; Tue, 26 Oct 2021 13:57:32 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:50326) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mfQcL-0006Mp-1x for help-guix@gnu.org; Tue, 26 Oct 2021 13:52:09 -0400 Received: from mx1.riseup.net ([198.252.153.129]:53274) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mfQcI-0003uH-JX for help-guix@gnu.org; Tue, 26 Oct 2021 13:52:08 -0400 Received: from fews1.riseup.net (fews1-pn.riseup.net [10.0.1.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 4Hdzst5Z1fzF3Th; Tue, 26 Oct 2021 10:52:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1635270722; bh=FAAvF/GxIwKXfiDpls6AnTJOuGb4bN3ZSZflY2q+sFI=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=kM/HSOU13k9H1P+SlXJZ2TcOBPvO86FNyulJ0Kya2VdLOvcD0o8rbGfa6BLk+nYdp rTebkZRgO+sfjCZd5wMke0nycLtirGrIIyYJgpTAIl4rCggG144T7CZdOTjUEUmLIu /sr3ukA+cOwwWLrtwYhS8Gh/lCZCi7D31mVGrTR4= X-Riseup-User-ID: 535FA48A7CB3567056FC2DEC02D0D8AEC7936F63BDA40227EBABEB723BF561A6 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews1.riseup.net (Postfix) with ESMTPSA id 4Hdzss6Svtz5vgB; Tue, 26 Oct 2021 10:52:01 -0700 (PDT) Date: Tue, 26 Oct 2021 06:24:29 +0200 From: raingloom To: Phil Beadling Subject: Re: Getting Unit Test Results Out Of Guix Build Message-ID: <20211026062429.242a504a@riseup.net> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Received-SPF: pass client-ip=198.252.153.129; envelope-from=raingloom@riseup.net; helo=mx1.riseup.net X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: help-guix Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: "Help-Guix" X-Migadu-Flow: FLOW_IN ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1635271055; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=h5bAKsfqUv5Akho64BndLO4iinHcSkfb8v7rrhBmkfs=; b=qHencZfz2jyevQvu7pkqAYawvKzfxyCZNQ3yRSak+hknHA9863xHz0Uod6NAy7PTPu2+WY kIpi79/UNr84+REVaTY2cx9pTnLhIzufVmv5PRQoDpUw3Q0zursLHFWKk7mrKJ3EF1GW58 ehlhSeOM9JVjO/RjPcJemMTUFgUVnEZuXHiG4j1g7EBOjInVZxxIpMqP3n+gI4cqzvl/qU cPPB81s89SRQG6tg0DHEw6X3ZwP8Oh0XSKHFWIRqR5cxgw0HPbzardDx2RpkWTStlhprkz BMqkD4lkU/CMOdQrJGi/lQwPDNaBrgWUl18z2Z1vHcQ60EHwej/b4SXKNerX6A== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1635271055; a=rsa-sha256; cv=none; b=faVQ28Pqg+EB9vvRyU8pjPKTQIaQVl1M788wsyDBhuVkqSmGcUJ1iI95b5qFDgWbznP+P7 zZsdsjjv8w5jWaDwxbOzxJ+8/5e7TINE+eVX/fnrloSrpPP3XwdJ5shUEfGi2OeP4qoVos 69M2fD/N+MzCleXd/xwxVhgM6ESGcIidG5bv+wbFtK/jHrtvIjLpA+S85wFJxb7B02GQfG o+0OOgCWSKRh3r/cZzoed8+i8sp2z36BIqk9jVZJ0jb7QfeGScRL8we/SNLUQRgtbdtstb JUQmzZe9ARmZV3bhIbe2Kn+g7YbdSNqg3CrhmhnXycW9YSvD/uusZjsnPNadvQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=riseup.net header.s=squak header.b="kM/HSOU1"; spf=pass (aspmx1.migadu.com: domain of help-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=help-guix-bounces@gnu.org X-Migadu-Spam-Score: -3.13 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=riseup.net header.s=squak header.b="kM/HSOU1"; dmarc=pass (policy=none) header.from=riseup.net; spf=pass (aspmx1.migadu.com: domain of help-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=help-guix-bounces@gnu.org X-Migadu-Queue-Id: 7FDEEAC84 X-Spam-Score: -3.13 X-Migadu-Scanner: scn0.migadu.com X-TUID: GLvq2vPEiGM0 On Mon, 25 Oct 2021 13:30:40 +0100 Phil Beadling 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.