Lines Matching +full:- +full:- +full:kernel +full:- +full:url

8 kernel during development), and our workloads can easily take down
9 boards when mistakes are made (kernel oopses, OOMs that take out
12 Mesa-LAVA software architecture
13 -------------------------------
15 The gitlab-runner will run on some host that has access to the LAVA
16 lab, with tags like "mesa-ci-x86-64-lava-$DEVICE_TYPE" to control only
18 gitlab-runner spawns a Docker container with lavacli in it, and
23 For a job, it will deploy the kernel, device tree, and the ramdisk
26 Deploying a new Mesa-LAVA lab
27 -----------------------------
34 The device type in lava-gitlab-ci.yml is the device type you create in
36 ``/etc/lava-dispatcher/device-types``.  You create your boards under
41 ``/etc/lava-dispatcher/device-types``).  Now, go find a relevant
47 to connect Mesa CI to it.  Install gitlab-runner and register as a
49 runner *must* have a tag (like "mesa-ci-x86-64-lava-rk3399-gru-kevin")
57 ``/etc/gitlab-runner/config.toml`` so it can access localhost.  Create a
58 gitlab-runner user in your LAVA instance, log in under that user on
62 .. code-block:: yaml
66     uri: <URL to the instance>
67     username: gitlab-runner
70 ``/etc/gitlab-runner/config.toml`` so that the Docker container can
73     volumes = ["/home/anholt/lava-config/lavacli.yaml:/root/.config/lavacli.yaml", "/cache"]
81 Now it's time to define your test jobs in the driver-specific
82 gitlab-ci.yml file, using the device-specific tags.