Skip to contentSkip to conversation

gitlab-ci: Test that "make check-kerneldoc" does not report any errors

PATCH In review Thomas Huth 2 participants 2 messages Jun 7, 2024 – Jun 14, 2024 KVM

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 gitlab-ci: Test that "make check-kerneldoc" does not report any errors

To make sure that we don't regress with the formatting of the comments, we should check this in the CI, too.

---
 .gitlab-ci.yml | 2 ++
 1 file changed, 2 insertions(+)
.gitlab-ci.yml +2 -0
index 23bb69e2..2af47328 100644
@@ -310,6 +310,8 @@ build-centos7:
      setjmp sieve tsc rmap_chain umip
      | tee results.txt
  - 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
Signature · 1 line
2.45.1
Reviewed-by on v1 1/1
#1 lore raw
Quoted 2 lines · Thomas Huth

To make sure that we don't regress with the formatting of the comments, we should check this in the CI, too.

Could make it a script, but this works well enough too.

Quoted 19 lines
---
 .gitlab-ci.yml | 2 ++
 1 file changed, 2 insertions(+)
.gitlab-ci.yml +2 -0
index 23bb69e2..2af47328 100644
@@ -310,6 +310,8 @@ build-centos7:
      setjmp sieve tsc rmap_chain umip
      | tee results.txt
  - 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