Lines Matching +full:piglit +full:- +full:traces +full:- +full:test
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``
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
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/``.
36 empty (or set to the default ``.gitlab-ci.yml``), and that the
51 bare-metal
55 Application traces replay
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
60 of those traces fail the pipeline fails as well. The second job replays traces listed in
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
63 has been granted access to these traces.
65 A traces YAML file also includes a ``download-url`` pointing to a MinIO
66 instance where to download the traces from. While the first job should always work with
67 publicly accessible traces, the second job could point to an url with restricted access.
69 Restricted traces are those that have been made available to Mesa developers without a
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
77 download and test them by themselves.
80 non-redistributable traces can request permission to Daniel Stone <daniels@collabora.com>.
82 gitlab.freedesktop.org accounts that are to be granted access to these traces will be
84 https://gitlab.freedesktop.org/freedesktop/helm-gitlab-config/-/commit/a3cd632743019f68ac8a829267de…
91 --------
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>`__.
107 `VK-GL-CTS <https://github.com/KhronosGroup/VK-GL-CTS>`__,
109 `Piglit <https://gitlab.freedesktop.org/mesa/piglit>`__,
117 it on ``#dri-devel`` on OFTC and tag `Nico Cortes
120 .. _CI-farm-expectations:
123 --------------------
126 unrelated work by other vendors, we require that a given driver's test
132 Additionally, the test farm needs to be able to provide a short enough
133 turnaround time that we can get our MRs through marge-bot without the
134 pipeline backing up. As a result, we require that the test farm be
138 If a test farm is short the HW to provide these guarantees, consider dropping
140 the run, and piglit logs the runtime of tests in the results.json.bz2 in the
144 .. code-block:: yaml
149 to just run 1/10th of the test list.
157 report to mesa-dev@lists.freedesktop.org after the fact explaining
162 ----------------
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 --------------
187 infrequently-updated build content like the CTS. The `freedesktop.org
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
216 ---------------------------------------
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 -----------------
260 -------------------------------
262 Gitlab CI usually runs a bleeding-edge kernel. The following documentation has