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

On Tue, 08 Jan 2019 09:35:33 +0100 Michael Albinus <michael.albinus@gmx.de> wrote: 

MA> Ted Zlatanov <tzz@lifelogs.com> writes:
>> 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.

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

MA> except:
MA>   changes:
MA>     - doc/**/*

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

It would break :) The `only` logic may be better here. But the
optimization won't buy us too much, because there aren't enough commits
per hour in the Emacs repo to stress the build runners, and builds are
easy to run in parallel with the Docker runner.

I think the important optimization is to shrink throughput time (the
time to do a build from trigger to finish) by pre-building the Docker
image with the packages instead of installing them every time. Also
running make with higher parallelism might help, I don't know for sure.

Ted



  reply	other threads:[~2019-01-09 14:01 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
2019-01-09 14:01             ` Ted Zlatanov [this message]
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=wonec4l6.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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).