marge-bot rebases and edits the commit message but there's not way for
it to introduce a memleak that wasn't spotted in the user pipeline
first. Since those tests are very flaky, let's skip them when running
the marge-bot pipeline.
Closes #1042
Part-of: <https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/1057>
LITEST_JOBS: 4
retry:
max: 2
+ rules:
+ - if: $GITLAB_USER_LOGIN != "marge-bot"
vm-valgrind-tap:
stage: valgrind
LITEST_JOBS: 4
retry:
max: 2
+ rules:
+ - if: $GITLAB_USER_LOGIN != "marge-bot"
vm-valgrind-touchpad-buttons:
stage: valgrind
LITEST_JOBS: 4
retry:
max: 2
+ rules:
+ - if: $GITLAB_USER_LOGIN != "marge-bot"
vm-valgrind-tablet:
stage: valgrind
LITEST_JOBS: 4
retry:
max: 2
+ rules:
+ - if: $GITLAB_USER_LOGIN != "marge-bot"
vm-valgrind-gestures-device:
stage: valgrind
LITEST_JOBS: 4
retry:
max: 2
+ rules:
+ - if: $GITLAB_USER_LOGIN != "marge-bot"
vm-valgrind-backends:
stage: valgrind
LITEST_JOBS: 4
retry:
max: 2
+ rules:
+ - if: $GITLAB_USER_LOGIN != "marge-bot"
vm-valgrind-misc:
stage: valgrind
LITEST_JOBS: 4
retry:
max: 2
+ rules:
+ - if: $GITLAB_USER_LOGIN != "marge-bot"
vm-valgrind-other devices:
stage: valgrind
LITEST_JOBS: 4
retry:
max: 2
+ rules:
+ - if: $GITLAB_USER_LOGIN != "marge-bot"
vm-valgrind-pointer:
stage: valgrind
LITEST_JOBS: 4
retry:
max: 2
+ rules:
+ - if: $GITLAB_USER_LOGIN != "marge-bot"
.fedora-build@template:
LITEST_JOBS: 4
retry:
max: 2
+ rules:
+ - if: $GITLAB_USER_LOGIN != "marge-bot"
{% endfor %}
{% endfor %}{# for if distro.use_for_qemu_tests #}