From: Rob Herring <robh@kernel.org>
To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Frank Rowand <frowand.list@gmail.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [RFC PATCH] of: Add a GitLab CI config file for unittests
Date: Fri, 30 Nov 2018 14:32:32 -0600 [thread overview]
Message-ID: <20181130203232.5743-1-robh@kernel.org> (raw)
This adds a GitLab CI config file running the DT unittest in a usermode
Linux build. The corresponding CI job can be found here:
https://gitlab.com/robherring/linux-dt-unittest/pipelines
This CI job can be duplicated by others by creating a kernel repo on a
GitLab instance and configuring GitLab CI to use
drivers/of/.gitlab-ci.yml config file.
Cc: Frank Rowand <frowand.list@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Rob Herring <robh@kernel.org>
---
drivers/of/.gitlab-ci.yml | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
create mode 100644 drivers/of/.gitlab-ci.yml
diff --git a/drivers/of/.gitlab-ci.yml b/drivers/of/.gitlab-ci.yml
new file mode 100644
index 000000000000..44a4824f5c33
--- /dev/null
+++ b/drivers/of/.gitlab-ci.yml
@@ -0,0 +1,18 @@
+# SPDX-License-Identifier: GPL-2.0+
+
+image: registry.gitlab.com/robherring/docker-images/ubuntu-kernel-build
+
+variables:
+ ARCH: um
+
+job-unittest:
+ artifacts:
+ paths:
+ - "*.log"
+
+ script:
+ - echo -e "CONFIG_OF=y\nCONFIG_OF_UNITTEST=y\nCONFIG_OF_OVERLAY=y" > kernel/configs/extra.config
+ - make defconfig extra.config
+ - make -s -j $(nproc) vmlinux | tee build.log
+ - TMP=/tmp ./vmlinux > boot.log || true
+ - grep -E '\#\#\# dt-test \#\#\# end of unittest - [0-9]* passed, 0 failed' boot.log
--
2.19.1
next reply other threads:[~2018-11-30 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 20:32 Rob Herring [this message]
2018-11-30 20:52 ` [RFC PATCH] of: Add a GitLab CI config file for unittests Daniel Vetter
2018-11-30 22:22 ` Rob Herring
2018-11-30 23:20 ` Daniel Vetter
2018-11-30 23:20 ` Daniel Vetter
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=20181130203232.5743-1-robh@kernel.org \
--to=robh@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.