All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Xen-devel <xen-devel@lists.xenproject.org>,
	Anthony PERARD <anthony.perard@vates.tech>,
	Michal Orzel <michal.orzel@amd.com>,
	Doug Goldstein <cardoe@cardoe.com>,
	Jason Andryuk <jason.andryuk@amd.com>,
	"Daniel P . Smith" <dpsmith@apertussolutions.com>
Subject: Re: [PATCH v2 2/7] Overhaul how Argo is built and packged
Date: Wed, 16 Apr 2025 12:21:33 +0200	[thread overview]
Message-ID: <Z_-ErdkJ3Gxs_vFN@mail-itl> (raw)
In-Reply-To: <44efebcd-877e-46a3-a072-07c44fc29f27@citrix.com>

[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]

On Wed, Apr 16, 2025 at 11:15:21AM +0100, Andrew Cooper wrote:
> On 16/04/2025 12:48 am, Stefano Stabellini wrote:
> > On Mon, 14 Apr 2025, Andrew Cooper wrote:
> >> Right now, the argo artefacts are a pile of files which the test has to turn
> >> back into something which resembles a filesystem.  Furthermore, because we do
> >> not build modules for the main kernel, it is extra important to make sure that
> >> xen-argo.ko doesn't get out of sync.
> >>
> >> Build argo conditionally as part of the linux artefact.  It's ~100kb all
> >> together, compared to ~14M for the kernel.
> >>
> >> Produce a single argo.cpio.gz with xen-argo.ko in the standard location.
> >> Prune userspace down to just the executables and libraries.
> >>
> >> This is cribbed from the existing scripts/x86_64-linux-argo.sh, which stays in
> >> place in the short term until Xen can be updated to use the new scheme.
> >>
> >> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> > Do we need to remove x86_64-argo-linux.sh?
> 
> Yes, but 4.20 still uses it.
> 
> One thing I'm not sure about is whether "keep latest artefact" is just
> artefacts from the latest run, or the latest of each named artefact.

I think it's latest run for a branch. If newer job (on a branch) doesn't
include an artifact anymore, it will be gone. Jobs referencing it won't
see it immediately, regardless of expire time.

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2025-04-16 10:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14 10:18 [PATCH TEST-ARTEFACTS v2 0/7] Rootfs/argo cleanup and microcode support Andrew Cooper
2025-04-14 10:18 ` [PATCH v2 1/7] Rename and adjust x86 containers Andrew Cooper
2025-04-14 11:12   ` Marek Marczykowski-Górecki
2025-04-14 10:18 ` [PATCH v2 2/7] Overhaul how Argo is built and packged Andrew Cooper
2025-04-14 10:35   ` Marek Marczykowski-Górecki
2025-04-14 10:38     ` Andrew Cooper
2025-04-14 10:55   ` Daniel P. Smith
2025-04-15 23:48   ` Stefano Stabellini
2025-04-16 10:15     ` Andrew Cooper
2025-04-16 10:21       ` Marek Marczykowski-Górecki [this message]
2025-04-14 10:18 ` [PATCH v2 3/7] Rework rootfs generation to make a cpio archive Andrew Cooper
2025-04-14 11:15   ` Marek Marczykowski-Górecki
2025-04-14 10:18 ` [PATCH v2 4/7] Shrink the rootfs substantially Andrew Cooper
2025-04-14 11:25   ` Marek Marczykowski-Górecki
2025-04-14 11:35     ` Andrew Cooper
2025-04-14 11:52   ` [PATCH v2.1 " Andrew Cooper
2025-04-14 14:22     ` Marek Marczykowski-Górecki
2025-04-14 10:18 ` [PATCH v2 5/7] Adjust directory layout for rootfs.cpio.gz Andrew Cooper
2025-04-14 14:21   ` Marek Marczykowski-Górecki
2025-04-14 10:18 ` [PATCH v2 6/7] Provide an ARM64 rootfs too Andrew Cooper
2025-04-14 14:23   ` Marek Marczykowski-Górecki
2025-04-14 10:18 ` [PATCH v2 7/7] Package microcode for the x86 hardware runners Andrew Cooper

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=Z_-ErdkJ3Gxs_vFN@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=cardoe@cardoe.com \
    --cc=dpsmith@apertussolutions.com \
    --cc=jason.andryuk@amd.com \
    --cc=michal.orzel@amd.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.
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.