This series adds another Gitlab-CI test running on a real hardware.
The gitlab-runner is connected to gitlab.com/xen-project/xen already.
Example test run (just subset of jobs scheduled):
https://gitlab.com/xen-project/people/marmarek/xen/-/pipelines/817952905

Details about the setup:
https://www.qubes-os.org/news/2022/05/05/automated-os-testing-on-physical-laptops/

Should there be some documentation (besides the above link) how to interact
with the CI system, for somebody else who could modify the test script? It's
rather tightly integrated with infrastructure that's outside of xen.git
control, so I'm not sure how practical that would be anyway.

Marek Marczykowski-Górecki (2):
  automation: update x86-64 tests to Linux 6.1.19
  automation: add a smoke and suspend test on an Alder Lake system

 automation/build/alpine/3.12-arm64v8.dockerfile      |   3 +-
 automation/gitlab-ci/build.yaml                      |   4 +-
 automation/gitlab-ci/test.yaml                       |  40 ++-
 automation/scripts/qubes-x86-64.sh                   | 174 ++++++++++++-
 automation/tests-artifacts/kernel/5.10.74.dockerfile |  38 +---
 automation/tests-artifacts/kernel/6.1.19.dockerfile  |  40 +++-
 6 files changed, 257 insertions(+), 42 deletions(-)
 create mode 100755 automation/scripts/qubes-x86-64.sh
 delete mode 100644 automation/tests-artifacts/kernel/5.10.74.dockerfile
 create mode 100644 automation/tests-artifacts/kernel/6.1.19.dockerfile

base-commit: b1f11273d5a774cc88a3685c96c2e7cf6385e3b6
-- 
git-series 0.9.1