Lines Matching +full:ci +full:- +full:deqp +full:- +full:artifacts
4 GitLab CI
5 ---------
8 We use it to test merge requests (MRs) before merging them (pre-merge testing),
9 as well as post-merge testing, for everything that hits ``main``
11 and even then the MR CI runs in the forked repository, which might have been
14 The CI runs a number of tests, from trivial build-testing to complex GPU rendering:
16 - Build testing for a number of build systems, configurations and platforms
17 - Sanity checks (``meson test``)
18 - Some drivers (softpipe, llvmpipe, freedreno and panfrost) are also tested
19 using `VK-GL-CTS <https://github.com/KhronosGroup/VK-GL-CTS>`__
20 - Replay of application traces
26 Due to limited resources, we currently do not run the CI automatically
30 If you're interested in the details, the main configuration file is ``.gitlab-ci.yml``,
31 and it references a number of other files in ``.gitlab-ci/``.
33 If the GitLab CI doesn't seem to be running on your fork (or MRs, as they run
35 Under "CI / CD" → "General pipelines", make sure "Custom CI config path" is
36 empty (or set to the default ``.gitlab-ci.yml``), and that the
39 If you're having issues with the GitLab CI, your best bet is to ask
45 The three GitLab CI systems currently integrated are:
51 bare-metal
56 -------------------------
58 The CI replays application traces with various drivers in two different jobs. The first
59 job replays traces listed in ``src/<driver>/ci/traces-<driver>.yml`` files and if any
61 ``src/<driver>/ci/restricted-traces-<driver>.yml`` and it is allowed to fail. This second
62 job is only created when the pipeline is triggered by `marge-bot` or any other user that
65 A traces YAML file also includes a ``download-url`` pointing to a MinIO
72 contributors without permissions to download non-redistributable traces can be merged
75 As an aside, only maintainers of such non-redistributable traces are responsible for
80 non-redistributable traces can request permission to Daniel Stone <daniels@collabora.com>.
84 https://gitlab.freedesktop.org/freedesktop/helm-gitlab-config/-/commit/a3cd632743019f68ac8a829267de…
87 to be added to the rules attribute of the Gitlab CI job that accesses the restricted
90 Intel CI
91 --------
93 The Intel CI is not yet integrated into the GitLab CI.
95 `the Intel CI configuration repo <https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins>`__
96 if you think you or Mesa would benefit from you having access to the Intel CI).
97 Results can be seen on `mesa-ci.01.org <https://mesa-ci.01.org>`__
100 `mesa-ci-results.jf.intel.com <http://mesa-ci-results.jf.intel.com>`__.
102 The Intel CI runs a much larger array of tests, on a number of generations
107 `VK-GL-CTS <https://github.com/KhronosGroup/VK-GL-CTS>`__,
108 `dEQP <https://android.googlesource.com/platform/external/deqp>`__,
116 If you're having issues with the Intel CI, your best bet is to ask about
117 it on ``#dri-devel`` on OFTC and tag `Nico Cortes
120 .. _CI-farm-expectations:
122 CI farm expectations
123 --------------------
128 driver had CI and failed once a week, we would be seeing someone's
133 turnaround time that we can get our MRs through marge-bot without the
139 tests to reduce runtime. dEQP job logs print the slowest tests at the end of
141 artifacts. Or, you can add the following to your job to only run some fraction
142 (in this case, 1/10th) of the deqp tests.
144 .. code-block:: yaml
151 If a HW CI farm goes offline (network dies and all CI pipelines end up
157 report to mesa-dev@lists.freedesktop.org after the fact explaining
162 ----------------
164 Mesa's CI is currently run primarily on packet.net's m1xlarge nodes
166 can speed up your personal CI builds (and marge-bot merges) by using a
167 faster personal machine as a runner. You can find the gitlab-runner
171 <https://docs.gitlab.com/ce/ci/runners/#create-a-specific-runner>`__ to
175 lines in ``/etc/gitlab-runner/config.toml``, for example::
184 --------------
186 The CI system uses Docker images extensively to cache
187 infrequently-updated build content like the CTS. The `freedesktop.org
188 CI templates
189 <https://gitlab.freedesktop.org/freedesktop/ci-templates/>`_ help us
197 not, the associated `.gitlab-ci/containers/<jobname>.sh`` will be run
206 bump the tag on each ``git commit --amend`` to your development
215 Building locally using CI docker images
216 ---------------------------------------
219 don't personally have. If you're experiencing this with the CI
223 Pulling docker image registry.freedesktop.org/anholt/mesa/debian/android_build:2020-09-11
227 go in _build, according to ``meson-build.sh``). We're going to be
228 using the image non-interactively so we use ``run --rm $IMAGE
229 command`` instead of ``run -it $IMAGE bash`` (which you may also find
231 .gitlab-ci.yml and run the CI meson build script:
233 .. code-block:: console
235 IMAGE=registry.freedesktop.org/anholt/mesa/debian/android_build:2020-09-11
237 …--rm -v `pwd`:/mesa -w /mesa $IMAGE env PKG_CONFIG_PATH=/usr/local/lib/aarch64-linux-android/pkgco…
242 .. code-block:: console
244 sudo docker run --rm -v `pwd`:/mesa $IMAGE ninja -C /mesa/_build
248 -----------------
250 Some conformance tests require a special treatment to be maintained on Gitlab CI.
259 Updating Gitlab CI Linux Kernel
260 -------------------------------
262 Gitlab CI usually runs a bleeding-edge kernel. The following documentation has
263 instructions on how to uprev Linux Kernel in the Gitlab Ci ecosystem.