Searched +full:vm +full:- +full:valgrind +full:- +full:touchpad (Results 1 – 2 of 2) sorted by relevance
9 # To change the gitlab CI, edit .gitlab-ci/ci.template and/or .gitlab-ci/config.yaml10 # and run ci-fairy generate-template. For details, see11 # https://freedesktop.pages.freedesktop.org/ci-templates/ci-fairy.html#templating-gitlab-ci-yml14 # - we really want to run dnf/apt/... only once, updating on the test runner for18 # This is handled by the ci-templates, ensuring containers are only rebuilt21 # - GitLab only allows one script: set per job but we have a bunch of commands22 # we need to re-run for each build (meson && ninja && etc). YAML cannot merge27 # MESON_ARGS=-Denable-something=true28 # NINJA_ARGS=dist ... to run 'ninja -C builddir dist'35 # e.g. fedora:31@build-default[all …]
1 .. _test-suite:11 $ sudo ./builddir/libinput-test-suite13 When developing libinput, the ``libinput-test-suite`` should always be15 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 run27 ``meson test -C builddir`` (or ``ninja test``). The ``libinput-test-suite`` is30 The upstream CI runs all these tests but not the ``libinput-test-suite``.33 .. _test-job-control:35 ------------------------------------------------------------------------------37 ------------------------------------------------------------------------------[all …]