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 4/6] gitlab-ci: Move check-kerneldoc test out of the centos test
Date: Fri, 26 Jul 2024 17:04:45 +1000 [thread overview]
Message-ID: <20240726070456.467533-5-npiggin@gmail.com> (raw)
In-Reply-To: <20240726070456.467533-1-npiggin@gmail.com>
This creates a new lightweight (alpine) kerneldoc check, based
on the QEMU static checking jobs.
The aim is to decouple the test build and run jobs on different
platforms from the static checker images, so one can be adjusted
without affecting the other.
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
---
.gitlab-ci.yml | 17 ++++++++++++++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 2d048b11d..0f72cefe7 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -305,7 +305,7 @@ build-centos8:
- 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 python39 qemu-kvm gcc
+ - yum install -y make qemu-kvm gcc
script:
- mkdir build
- cd build
@@ -343,8 +343,6 @@ build-centos8:
| 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`
# Cirrus-CI provides containers with macOS and Linux with KVM enabled,
# so we can test some scenarios there that are not possible with the
@@ -418,3 +416,16 @@ s390x-kvm:
only:
variables:
- $S390X_Z15_RUNNER_AVAILABLE
+
+check-kerneldoc:
+ extends: .intree_template
+ stage: build
+ image: python:3.10-alpine
+ needs: []
+ script:
+ - ./configure --arch=x86_64
+ - make -s check-kerneldoc 2>&1 | tee docwarnings.txt
+ - test -z `cat docwarnings.txt`
+ before_script:
+ - apk -U add bash make perl gcc
+ allow_failure: true
--
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 ` [kvm-unit-tests PATCH 3/6] gitlab-ci: upgrade to CentOS 8 Nicholas Piggin
2024-07-26 7:04 ` Nicholas Piggin [this message]
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-5-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