[PATCH 0/3] automation: introduce an x86_64 Dom0/DomU test

Stefano Stabellini posted 3 patches 2 years, 6 months ago
Failed in applying to current master (apply log)
There is a newer version of this series
automation/gitlab-ci/build.yaml                    | 24 ++++++
automation/gitlab-ci/test.yaml                     | 24 ++++++
automation/scripts/qemu-alpine-x86_64.sh           | 92 ++++++++++++++++++++++
automation/tests-artifacts/alpine/3.12.dockerfile  | 68 ++++++++++++++++
.../tests-artifacts/kernel/5.10.74.dockerfile      | 38 +++++++++
5 files changed, 246 insertions(+)
create mode 100644 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
[PATCH 0/3] automation: introduce an x86_64 Dom0/DomU test
Posted by Stefano Stabellini 2 years, 6 months ago
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           | 92 ++++++++++++++++++++++
 automation/tests-artifacts/alpine/3.12.dockerfile  | 68 ++++++++++++++++
 .../tests-artifacts/kernel/5.10.74.dockerfile      | 38 +++++++++
 5 files changed, 246 insertions(+)
 create mode 100644 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

Re: [PATCH 0/3] automation: introduce an x86_64 Dom0/DomU test
Posted by Ian Jackson 2 years, 6 months ago
Stefano Stabellini writes ("[PATCH 0/3] automation: introduce an x86_64 Dom0/DomU test"):
> 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.

Thanks.  For 4.16:

Release-Acked-by: Ian Jackson <iwj@xenproject.org>