From patchwork Tue Oct 26 01:37:20 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Stefano Stabellini X-Patchwork-Id: 12583753 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E8E3EC433EF for ; Tue, 26 Oct 2021 01:37:34 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A68EE60EBC for ; Tue, 26 Oct 2021 01:37:34 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org A68EE60EBC Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.xenproject.org Received: from list by lists.xenproject.org with outflank-mailman.216146.375635 (Exim 4.92) (envelope-from ) id 1mfBP2-0000A5-UZ; Tue, 26 Oct 2021 01:37:24 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 216146.375635; Tue, 26 Oct 2021 01:37:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mfBP2-00009s-QO; Tue, 26 Oct 2021 01:37:24 +0000 Received: by outflank-mailman (input) for mailman id 216146; Tue, 26 Oct 2021 01:37:22 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mfBP0-00009k-Pi for xen-devel@lists.xenproject.org; Tue, 26 Oct 2021 01:37:22 +0000 Received: from mail.kernel.org (unknown [198.145.29.99]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id 4360f0c3-35fd-11ec-8420-12813bfff9fa; Tue, 26 Oct 2021 01:37:21 +0000 (UTC) Received: by mail.kernel.org (Postfix) with ESMTPSA id 093FA60EBC; Tue, 26 Oct 2021 01:37:20 +0000 (UTC) X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: 4360f0c3-35fd-11ec-8420-12813bfff9fa DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1635212241; bh=wqAGzrvlFE6wtuBFH9ll5fseQhx/ylvsfjmPPJUxAQc=; h=Date:From:To:cc:Subject:From; b=gktLmHmnVfYHSmlPbak7OouVwr9UpcENPgC2OEPH3Mp1b3A0wkJo84/hhlyLdVMh8 AgS/FACJToSsPES3hgcbpzzyqLKgX1DKh/nHA2bMQKxDVN5KEdJ5+/Lzo2ly9FK/9p c6GkLSyzQU1ADIF+ecwuOxD/Kp/F8mPSl/BBEjgv444Hhs6Dwoh84j8SzeDJcxn8ek Kl7tE4fnTZRgsQmvIXInuw1ZLN17Z+99jUtDeTLwhUtleKNmU9zPw03mBjO7TzA9Am XpVjb6s1NnAtlIQIkdLkdNolIFyYKGBG+YljKh3P742izdyHvyh53VFLf6+EMFw3BS f977Bybf6kftw== Date: Mon, 25 Oct 2021 18:37:20 -0700 (PDT) From: Stefano Stabellini X-X-Sender: sstabellini@sstabellini-ThinkPad-T480s To: xen-devel@lists.xenproject.org cc: sstabellini@kernel.org, iwj@xenproject.org, cardoe@cardoe.com, wl@xen.org, andrew.cooper3@citrix.com, anthony.perard@citrix.com Subject: [PATCH v2 0/3] automation: introduce an x86_64 Dom0/DomU test Message-ID: User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Hi all, This small patch series introduces a new QEMU-based test to Gitlab-CI. It uses QEMU to emulate an x86_64 machine and run Xen, Dom0 and start a DomU. It is very similar to the existing qemu-alpine-arm64-gcc test but based on x86_64 rather than ARM64. I think it is important because all the other x86_64 gitlab-ci tests we currently have are more narrow and based on XTF. This would be the first end-to-end x86_64 test in gitlab-ci. To make it happen, we need an Alpine Linux rootfs and a Linux kernel. The first two patches introduce them to gitlab-ci. Note that actually nothing will get build during gitlab-ci runs, it has already been done beforehand and uploaded as containers. They only import *existing* containers and binaries into a gitlab-ci run, thus, they cannot fail. The risk to the release of the first two patches is as close to zero as possible. The last patch is the one introducing a new test. This one can fail. However, it is a new test at the end of the pipeline: it doesn't impact the existing tests. In the worst case, the test will fail and the whole pipeline will be marked as "failed" but looking at the jobs all the other will continue to be marked as successful. In short, if it fails, we can simply ignore it. Also, at the moment it is actually succeeding. Cheers, Stefano Stefano Stabellini (3): automation: add x86_64 alpine 3.12 test-artifact automation: Linux 5.10.74 test-artifact automation: add a QEMU based x86_64 Dom0/DomU test automation/gitlab-ci/build.yaml | 24 ++++++ automation/gitlab-ci/test.yaml | 24 ++++++ automation/scripts/qemu-alpine-x86_64.sh | 95 ++++++++++++++++++++++ automation/tests-artifacts/alpine/3.12.dockerfile | 66 +++++++++++++++ .../tests-artifacts/kernel/5.10.74.dockerfile | 38 +++++++++ 5 files changed, 247 insertions(+) create mode 100755 automation/scripts/qemu-alpine-x86_64.sh create mode 100644 automation/tests-artifacts/alpine/3.12.dockerfile create mode 100644 automation/tests-artifacts/kernel/5.10.74.dockerfile