From: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Petri Latvala <petri.latvala@intel.com>
Subject: [igt-dev] [PATCH v2 i-g-t] ci: build with Clang
Date: Tue, 30 Apr 2019 14:19:01 +0300 [thread overview]
Message-ID: <20190430111901.21917-1-arkadiusz.hiler@intel.com> (raw)
In-Reply-To: <20190424161526.19208-1-simon.ser@intel.com>
From: Simon Ser <simon.ser@intel.com>
This adds a build and test step with Clang on Fedora. Hopefully this can
help keeping Clang builds healthy.
Signed-off-by: Simon Ser <simon.ser@intel.com>
Acked-by: Petri Latvala <petri.latvala@intel.com>
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
---
Completed pipeline:
https://gitlab.freedesktop.org/ivyl/igt/pipelines/33973
.gitlab-ci.yml | 19 +++++++++++++++++++
Dockerfile.fedora | 3 +++
2 files changed, 22 insertions(+)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index ae8cbb67..f282c684 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -47,6 +47,17 @@ build:tests-fedora-oldest-meson:
- ninja -C build
- ninja -C build igt-gpu-tools-doc
+build:tests-fedora-clang:
+ stage: build
+ variables:
+ CC: clang
+ script:
+ - meson $MESON_OPTIONS build
+ - ninja -C build
+ artifacts:
+ paths:
+ - build
+
build:tests-debian-meson:
image: $CI_REGISTRY/$CI_PROJECT_PATH/igt-debian:latest
stage: build
@@ -99,6 +110,14 @@ test:ninja-test:
stage: test
script: ninja -C build test
+test:ninja-test-clang:
+ dependencies:
+ - build:tests-fedora-clang
+ variables:
+ CC: clang
+ stage: test
+ script: ninja -C build test
+
test:ninja-test-arm64:
image: $CI_REGISTRY/$CI_PROJECT_PATH/igt-debian-arm64:latest
dependencies:
diff --git a/Dockerfile.fedora b/Dockerfile.fedora
index 29520f7b..0795de0e 100644
--- a/Dockerfile.fedora
+++ b/Dockerfile.fedora
@@ -35,6 +35,9 @@ RUN tar xf peg-0.1.18.tar.gz
RUN cd peg-0.1.18 && make PREFIX=/usr install
RUN rm -fr /tmp/peg
+# For compile-testing on clang
+RUN dnf install -y clang
+
# Meson version switching shenanigans
WORKDIR /usr/src
RUN curl -O https://files.pythonhosted.org/packages/17/d0/0fe98a9557a2f07dbe6f99ef57f2bc37450b641e1f6ceae9ce04c3c845dd/meson-0.46.0.tar.gz
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-04-30 11:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 16:15 [igt-dev] [PATCH i-g-t] ci: build with Clang Simon Ser
2019-04-24 18:40 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-04-25 5:09 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-04-25 7:35 ` [igt-dev] [PATCH i-g-t] " Daniel Vetter
2019-04-25 7:36 ` Daniel Vetter
2019-04-25 10:05 ` Jani Nikula
2019-04-25 13:49 ` Daniel Vetter
2019-04-25 13:54 ` Ser, Simon
2019-04-25 14:08 ` Arkadiusz Hiler
2019-04-25 14:00 ` Arkadiusz Hiler
2019-04-25 14:56 ` Ville Syrjälä
2019-04-30 11:11 ` Arkadiusz Hiler
2019-04-25 11:22 ` Ser, Simon
2019-04-25 11:45 ` Petri Latvala
2019-04-25 13:46 ` Daniel Vetter
2019-04-25 13:50 ` Arkadiusz Hiler
2019-04-30 11:19 ` Arkadiusz Hiler [this message]
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=20190430111901.21917-1-arkadiusz.hiler@intel.com \
--to=arkadiusz.hiler@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@intel.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