unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: emacs-devel@gnu.org
Subject: Re: filenotify-tests.el failing inside Docker debian:stretch
Date: Tue, 08 Jan 2019 09:35:33 +0100	[thread overview]
Message-ID: <87y37vpmwa.fsf@gmx.de> (raw)
In-Reply-To: <imz0dv41.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 07 Jan 2019 21:18:54 +0000")

Ted Zlatanov <tzz@lifelogs.com> writes:

Hi Ted,

> MA> Finally, I've ended up with the appended .gitlab-ci.yml file. Is it OK
> MA> to push it to master?
>
> Yes, absolutely. The change looks good.

Done.

> After that merge, I will work on speeding up the build but I think once
> we have passing builds we can open EMBA to public read-only access.

One idea is to exclude *.texi changes from test-all runs. Something like
(untested)

except:
  changes:
    - doc/**/*

I have no idea what happens, if a lisp file and a texi file are touched
in the same commit.

> Thank you for working on this!
> Ted

Best regards, Michael.



  reply	other threads:[~2019-01-08  8:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-31 16:14 filenotify-tests.el failing inside Docker debian:stretch Ted Zlatanov
2018-12-31 17:27 ` Michael Albinus
2018-12-31 18:48   ` Ted Zlatanov
2018-12-31 19:39     ` Ted Zlatanov
2019-01-02  8:36     ` Michael Albinus
2019-01-02 14:19       ` Ted Zlatanov
2019-01-06 15:40     ` Michael Albinus
2019-01-07 13:17       ` Michael Albinus
2019-01-07 21:18         ` Ted Zlatanov
2019-01-08  8:35           ` Michael Albinus [this message]
2019-01-09 14:01             ` Ted Zlatanov
2019-01-02  8:31 ` Michael Albinus
2019-01-02 14:16   ` Ted Zlatanov
2019-01-02 14:31     ` Michael Albinus
2019-01-02 14:40       ` Ted Zlatanov
2019-01-02 14:48         ` Michael Albinus
2019-01-02 17:10           ` Ted Zlatanov
2019-01-03 14:32             ` Michael Albinus
2019-01-03 15:50               ` Ted Zlatanov

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=87y37vpmwa.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    /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).