Home
last modified time | relevance | path

Searched +full:vm +full:- +full:touchpad (Results 1 – 2 of 2) sorted by relevance

/third_party/libinput/
D.gitlab-ci.yml9 # To change the gitlab CI, edit .gitlab-ci/ci.template and/or .gitlab-ci/config.yaml
10 # and run ci-fairy generate-template. For details, see
11 # https://freedesktop.pages.freedesktop.org/ci-templates/ci-fairy.html#templating-gitlab-ci-yml
14 # - we really want to run dnf/apt/... only once, updating on the test runner for
18 # This is handled by the ci-templates, ensuring containers are only rebuilt
21 # - GitLab only allows one script: set per job but we have a bunch of commands
22 # we need to re-run for each build (meson && ninja && etc). YAML cannot merge
27 # MESON_ARGS=-Denable-something=true
28 # NINJA_ARGS=dist ... to run 'ninja -C builddir dist'
35 # e.g. fedora:31@build-default
[all …]
/third_party/libinput/doc/user/
Dtest-suite.rst1 .. _test-suite:
11 $ sudo ./builddir/libinput-test-suite
13 When developing libinput, the ``libinput-test-suite`` should always be
15 the number of tests to run can be filtered, see :ref:`test-filtering`.
17 touchpad tap-to-click) while hacking on that specific feature and only run
27 ``meson test -C builddir`` (or ``ninja test``). The ``libinput-test-suite`` is
30 The upstream CI runs all these tests but not the ``libinput-test-suite``.
33 .. _test-job-control:
35 ------------------------------------------------------------------------------
37 ------------------------------------------------------------------------------
[all …]