From: Michael Albinus <michael.albinus@gmx.de>
To: dick <dick.r.chiang@gmail.com>
Cc: 51902@debbugs.gnu.org
Subject: bug#51902: 28.0.50; [PATCH] Get mh-e tests to pass
Date: Wed, 17 Nov 2021 09:40:10 +0100 [thread overview]
Message-ID: <87sfvvp445.fsf@gmx.de> (raw)
In-Reply-To: <8735nvws3j.fsf@dick> (dick's message of "Tue, 16 Nov 2021 19:20:16 -0500")
dick <dick.r.chiang@gmail.com> writes:
> diff --git a/test/infra/gitlab-ci.yml b/test/infra/gitlab-ci.yml
> index 001c779572..43897a9fe9 100644
> --- a/test/infra/gitlab-ci.yml
> +++ b/test/infra/gitlab-ci.yml
> @@ -248,6 +248,13 @@ test-lisp-net-inotify:
> target: emacs-inotify
> make_params: "-C test check-lisp-net"
>
> +test-lisp-mh-e-inotify:
> + stage: normal
> + extends: [.job-template, .test-template]
> + variables:
> + target: emacs-inotify
> + make_params: "-C test check-lisp-mh-e"
> +
> build-image-filenotify-gio:
> stage: platform-images
> extends: [.job-template, .build-template, .filenotify-gio-template]
Looks OK to me. Perhaps it could be added prior test-lisp-net-inotify,
keeping alphabetical order?
Bonus points, if the rules for this job (and test-lisp-inotify,
test-lisp-net-inotify) could be adapted, that these jobs run only when
there are relevant changes.
Best regards, Michael.
prev parent reply other threads:[~2021-11-17 8:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 0:20 bug#51902: 28.0.50; [PATCH] Get mh-e tests to pass dick
2021-11-17 8:06 ` Lars Ingebrigtsen
2021-11-17 14:46 ` Stephen Gildea
2021-11-17 16:16 ` Mike Kupfer
2021-11-17 16:23 ` Stephen Gildea
2021-11-17 17:15 ` Mike Kupfer
2021-11-17 17:34 ` Stephen Gildea
2021-11-17 17:45 ` dick
2021-11-17 19:39 ` Mike Kupfer
2021-11-18 16:30 ` Stephen Gildea
2021-11-18 8:23 ` Michael Albinus
2021-11-17 8:40 ` Michael Albinus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfvvp445.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=51902@debbugs.gnu.org \
--cc=dick.r.chiang@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).