[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v1 8/8] automation: add RISC-V smoke test
- To: Oleksii Kurochko <oleksii.kurochko@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- From: Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>
- Date: Fri, 6 Jan 2023 15:05:10 +0000
- Accept-language: en-GB, en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=pe0jS5A0aRzTdLML3t90WfHJv8bffJSIVdsTEe5UdMk=; b=VvKg+LCkeRYoVcIL3Xqy3msz+pOic9vIbFH0xgJ5pOUo2ywNcbkgCXj19b194dsrsbTlJeL7mvmvISvNBtbv9tcsYgJURuxVefIcwEei+/6BsEqVpoHVqi/HvJ2Ma7VkqC1BmCZGt5y8H5XLB+JZcPnVQtqvrVkClmLyV749L5LCr4cZOY3g9a3m0m0fYI86IeaifqAFVboIdxLbgcQXkYIKI73Mr+Qeb2CTuQZf+19lvWMJN4c5brhbay8Dk3suOe9wxkR2MidRO4B0yaYfYTTrxHHh8gsqeh0je7uZ0VDMnpd0DmF2WToy5fm6vtfOU1zulFGlMFg2PnhyJmNowA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hxwcozv58hzWGjZOhl/wdeG1mja8/ArtjWt7beR03BTma8/G35ymEVAQh2KdamLVcfr8/XuZs57LikOKxv/AFktKe+dvfOixh0m8uhblFbVunAqduwmP/LlxAwyBE4HuilIK2SIe2YmEe29Z9b5WSF0/8euEjldETkb5iAddDQRXk06g5FGnFEhI0u3OvBFD2GZak3tU09NIhb26N5q6fWb1WZM2pQtaQ+VL7d5fc49CRRzx++/9kCs/4B1BopRlBFu0tEyK0HcDmSTiGp68AEz5FCCaliO+cMLsXt+CsAnzJIS/lNH5ZOd9VrDMapxouBympihPQ6I1d7IcfQjsZA==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=citrix.com;
- Cc: Stefano Stabellini <sstabellini@xxxxxxxxxx>, Gianluca Guida <gianluca@xxxxxxxxxxxx>, Doug Goldstein <cardoe@xxxxxxxxxx>
- Delivery-date: Fri, 06 Jan 2023 15:05:22 +0000
- Ironport-data: A9a23:OE9KcqN4zexMOkTvrR1GlsFynXyQoLVcMsEvi/4bfWQNrUor1zQBy mEWUW/UbPaOamqgLt1xOYuz9hkBuZTQzdAwTAto+SlhQUwRpJueD7x1DKtS0wC6dZSfER09v 63yTvGacajYm1eF/k/F3oDJ9CU6jufQA+KmU4YoAwgpLSd8UiAtlBl/rOAwh49skLCRDhiE/ Nj/uKUzAnf8s9JPGj9SuvzrRC9H5qyo42tB5gJmP5ingXeF/5UrJMNHTU2OByOQrrl8RoaSW +vFxbelyWLVlz9F5gSNy+uTnuUiG9Y+DCDW4pZkc/HKbitq/0Te5p0TJvsEAXq7vh3S9zxHJ HehgrTrIeshFvWkdO3wyHC0GQkmVUFN0OevzXRSLaV/ZqAJGpfh66wGMa04AWEX0uFlWTgU/ s1AFDAqR0G9m6WnnpmrcsA506zPLOGzVG8ekldJ6GiASN0BGNXESaiM4sJE1jAtgMwIBezZe 8cSdTtoalLHfgFLPVAUTpk5mY9EhFGmK2Ee9A3T+PRxujeLpOBy+OGF3N79U9qGX8hK2G2fo XrL5T/RCRAGLt2PjzGC9xpAg8eexHKjA95CSdVU8NZrsFKXn1I3CyFVdni4ndW7lxSZXvB2f hl8Fi0G6PJaGFaQZt75Uh6joX/CvQMGXNFQEOoS5wSEy66S6AGcbkAUQzgEZNE4ucseQT0xy kTPj97vHSZosrCeVTSa7Lj8hSipJSEfIGsGZCkFZQgI+d/upMc0lB2nZtliGaixk9b8MSvx3 TeRrS41wb4UiKYj3Kyh8VfKqzmlvJTOQ0g+4QC/Y46+xgZwZYrgbIvx71HetK9ENNzAEQHHu 2UYkc+D6uxIFYuKiCGGXOQKGveu+uqBNzrfx1VoGvHN6giQxpJqRqgIiBkWGaujGp9slePBC KMLhT5s2Q==
- Ironport-hdrordr: A9a23:f6FWVqirmHkD/M179Y38v0gT1nBQXugji2hC6mlwRA09TyX4rb HJoB1/73XJYVkqKRMdcLy7Sc29qBDnm6Kdg7NhXouKZwXvsmqvMJxe9oPpwTH6chefygc178 4JGJSWY+eAaGSS4/yKhzVQ0OxN/DBEys2VbCvloEuFhDsKV51d
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Thread-index: AQHZIdDdCltTrKYYX0C6LpSEFhyV666RfOgA
- Thread-topic: [PATCH v1 8/8] automation: add RISC-V smoke test
On 06/01/2023 1:14 pm, Oleksii Kurochko wrote:
> Add check if there is a message 'Hello from C env' presents
> in log file to be sure that stack is set and C part of early printk
> is working.
>
> Also qemu-system-riscv was added to riscv64.dockerfile as it is
> required for RISC-V smoke test.
>
> Signed-off-by: Oleksii Kurochko <oleksii.kurochko@xxxxxxxxx>
> ---
> automation/build/archlinux/riscv64.dockerfile | 3 ++-
> automation/scripts/qemu-smoke-riscv64.sh | 20 +++++++++++++++++++
> 2 files changed, 22 insertions(+), 1 deletion(-)
> create mode 100755 automation/scripts/qemu-smoke-riscv64.sh
Looking through the entire series, aren't we missing a hunk to test.yml
to wire up the smoke test?
It wants to live in this patch along with the introduction of
qemu-smoke-riscv64.sh
However, the modification to the dockerfile want breaking out and
submitted separately. It will involve rebuilding and redeploying the
container, which is a) fine to do separately, and b) a necessary
prerequisite for anyone else to take this series and test it.
~Andrew
|
