From: Nicholas Piggin <npiggin@gmail.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Nicholas Piggin <npiggin@gmail.com>,
Andrew Jones <andrew.jones@linux.dev>,
kvm@vger.kernel.org
Subject: [kvm-unit-tests PATCH 3/6] gitlab-ci: upgrade to CentOS 8
Date: Fri, 26 Jul 2024 17:04:44 +1000 [thread overview]
Message-ID: <20240726070456.467533-4-npiggin@gmail.com> (raw)
In-Reply-To: <20240726070456.467533-1-npiggin@gmail.com>
CentOS 7 reached EOL at the end of June 2024. Upgrade to CentOS 8.
The mirror URL adjustment script still seems to be required.
This brings across some of the x86-64 tests that had been enabled
on the fedora build as well.
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
---
.gitlab-ci.yml | 40 +++++++++++++++++++++++++++++++++-------
1 file changed, 33 insertions(+), 7 deletions(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 823f03c3e..2d048b11d 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -296,26 +296,52 @@ build-clang:
| tee results.txt
- grep -q PASS results.txt && ! grep -q FAIL results.txt
-build-centos7:
+build-centos8:
extends: .outoftree_template
- image: centos:7
+ image: centos:8
before_script:
# CentOS mirrors have changed, these sed scripts fixes the repos.
- sed -i s/mirror.centos.org/vault.centos.org/g /etc/yum.repos.d/*.repo
- sed -i s/^#.*baseurl=http/baseurl=http/g /etc/yum.repos.d/*.repo
- sed -i s/^mirrorlist=http/#mirrorlist=http/g /etc/yum.repos.d/*.repo
- yum update -y
- - yum install -y make python qemu-kvm gcc
+ - yum install -y make python39 qemu-kvm gcc
script:
- mkdir build
- cd build
- ../configure --arch=x86_64 --disable-pretty-print-stacks
- make -j2
- ACCEL=tcg ./run_tests.sh
- vmexit_cpuid vmexit_mov_from_cr8 vmexit_mov_to_cr8 vmexit_inl_pmtimer
- vmexit_ple_round_robin vmexit_tscdeadline vmexit_tscdeadline_immed port80
- setjmp sieve tsc rmap_chain umip
- | tee results.txt
+ eventinj
+ intel_iommu
+ ioapic-split
+ memory
+ pks
+ pku
+ port80
+ rdpru
+ rmap_chain
+ setjmp
+ sieve
+ smap
+ smptest
+ smptest3
+ syscall
+ tsc
+ umip
+ vmexit_cpuid
+ vmexit_cr0_wp
+ vmexit_cr4_pge
+ vmexit_inl_pmtimer
+ vmexit_ipi
+ vmexit_ipi_halt
+ vmexit_mov_from_cr8
+ vmexit_mov_to_cr8
+ vmexit_ple_round_robin
+ vmexit_tscdeadline
+ vmexit_tscdeadline_immed
+ | tee results.txt
+ - if grep -q FAIL results.txt ; then exit 1 ; fi
- grep -q PASS results.txt && ! grep -q FAIL results.txt
- make -s check-kerneldoc 2>&1 | tee docwarnings.txt
- test -z `cat docwarnings.txt`
--
2.45.2
next prev parent reply other threads:[~2024-07-26 7:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 7:04 [kvm-unit-tests PATCH 0/6] Checking and CI improvements Nicholas Piggin
2024-07-26 7:04 ` [kvm-unit-tests PATCH 1/6] gitlab-ci: fix CentOS mirror list Nicholas Piggin
2024-07-26 7:04 ` [kvm-unit-tests PATCH 2/6] arm: Fix kerneldoc Nicholas Piggin
2024-07-26 9:40 ` Suzuki K Poulose
2024-07-26 7:04 ` Nicholas Piggin [this message]
2024-07-26 7:04 ` [kvm-unit-tests PATCH 4/6] gitlab-ci: Move check-kerneldoc test out of the centos test Nicholas Piggin
2024-07-26 7:04 ` [kvm-unit-tests PATCH 5/6] gitlab-ci: add a shellcheck test Nicholas Piggin
2024-07-26 7:04 ` [kvm-unit-tests PATCH 6/6] checkpatch support Nicholas Piggin
2024-07-29 13:12 ` [kvm-unit-tests PATCH 0/6] Checking and CI improvements Andrew Jones
2024-08-12 14:32 ` Andrew Jones
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=20240726070456.467533-4-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=andrew.jones@linux.dev \
--cc=kvm@vger.kernel.org \
--cc=thuth@redhat.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