all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philipp <p.stephani2@gmail.com>
To: Pip Cet <pipcet@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: Run (some) tests more automagically?
Date: Sun, 21 Feb 2021 15:45:41 +0100	[thread overview]
Message-ID: <56BEEC4F-1FDC-4AD1-8165-D4C542D0F56C@gmail.com> (raw)
In-Reply-To: <CAOqdjBdLVYmzRfxLdXdszfaRnzp7vUdG6Q0zJbHCXoUzjAM3PA@mail.gmail.com>



> Am 21.02.2021 um 15:28 schrieb Pip Cet <pipcet@gmail.com>:
> 
> 
> Speaking of code changes, one thing I'm worried about is that one
> developer on, say, Windows does something, forgets to adjust the tests
> so there's a spurious failure on GNU/Linux, and then the next
> GNU/Linux developer to touch the file will see a test failure that has
> nothing to do with their changes. I don't have a good solution for
> that one.

The typical solution is to run CI pipelines for all supported platforms and not allow pushing commits that fail any of the pipelines.  In the context of Emacs, there are still some downsides to this: it would require running nonfree OSes, and right now the CI pipelines are still a bit slow.


  reply	other threads:[~2021-02-21 14:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-21 13:25 Run (some) tests more automagically? Lars Ingebrigtsen
2021-02-21 13:48 ` dick.r.chiang
2021-02-21 14:28 ` Pip Cet
2021-02-21 14:45   ` Philipp [this message]
2021-02-21 16:05   ` Lars Ingebrigtsen
2021-02-21 15:37 ` Eli Zaretskii
2021-02-21 15:57   ` Lars Ingebrigtsen
2021-02-24 10:42 ` Phillip Lord
2021-02-24 14:34   ` Lars Ingebrigtsen
2021-02-26 11:44     ` Phillip Lord
2021-02-26 11:50       ` Lars Ingebrigtsen
2021-03-01 17:50         ` Phillip Lord

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56BEEC4F-1FDC-4AD1-8165-D4C542D0F56C@gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=pipcet@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.