($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: ross.burton@arm.com
To: meta-arm@lists.yoctoproject.org
Cc: nd@arm.com
Subject: [PATCH 4/4] CI: build both aarch64 and x86-64 packages for as muny FVPs as possible
Date: Tue, 24 Oct 2023 14:52:36 +0100	[thread overview]
Message-ID: <20231024135236.3510412-4-ross.burton@arm.com> (raw)
In-Reply-To: <20231024135236.3510412-1-ross.burton@arm.com>

From: Ross Burton <ross.burton@arm.com>

Some FVPs are available as x86-64 and aarch64 binaries, so build target
(qemuarm64) and nativesdk (x86-64) packages for these to verify the
checksums are correct.

Signed-off-by: Ross Burton <ross.burton@arm.com>
---
 ci/fvps.yml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/ci/fvps.yml b/ci/fvps.yml
index 1bced299..a89df053 100644
--- a/ci/fvps.yml
+++ b/ci/fvps.yml
@@ -14,6 +14,10 @@ local_conf_header:
     SDKMACHINE = "x86_64"
 
 target:
+  # Target packages to test aarch64
+  - fvp-base-a-aem
+  - fvp-corstone1000
+  # Nativesdk to test x86-64
   - nativesdk-fvp-base-a-aem
   - nativesdk-fvp-corstone1000
   - nativesdk-fvp-n1-edge
-- 
2.34.1



  parent reply	other threads:[~2023-10-24 13:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 13:52 [PATCH 1/4] arm/fvp-corstone1000: upgrade to 11.22.35, add aarch64 binaries ross.burton
2023-10-24 13:52 ` [PATCH 2/4] kas/corstone1000: don't limit the FVP use to x86-64 ross.burton
2023-10-24 13:52 ` [PATCH 3/4] CI: don't pin corstone1000-fvp " ross.burton
2023-10-24 13:52 ` ross.burton [this message]
2023-10-25  1:29 ` [PATCH 1/4] arm/fvp-corstone1000: upgrade to 11.22.35, add aarch64 binaries Jon Mason

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=20231024135236.3510412-4-ross.burton@arm.com \
    --to=ross.burton@arm.com \
    --cc=meta-arm@lists.yoctoproject.org \
    --cc=nd@arm.com \
    /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).