unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tim Landscheidt <tim@tim-landscheidt.de>
To: emacs-devel@gnu.org
Subject: Re: Multi-OS Emacs buildbot?
Date: Sun, 20 Dec 2020 06:54:10 +0000	[thread overview]
Message-ID: <87czz5ynl9.fsf@passepartout.tim-landscheidt.de> (raw)
In-Reply-To: 871rfl9pd4.fsf@codeisgreat.org

Pankaj Jangid <pankaj@codeisgreat.org> wrote:

>>> Okay. Let me write and come up with something. I take this up.

>> Hey, hang on a minute.  :-)  I appreciate the enthusiasm, but we should
>> first decide whether we want this or not.  And remember, Dick promised
>> to set up a real multi-platform CI thing at some buildbot service or
>> other, and we won't need this super-simple one then.

> Definitely I was going to hold till today. I was very late. :-) Read the
> whole thread now. Looks like we already have most parts.

> Even if that infrastruction is ready, I would certainly want a script to
> find out the commit that broke the build on my hardware. That reverse
> choronological loop.

> If someone has that ready then please share. Or may be that could be
> part of the repository.

I'm not sure what you mean exactly.  If you want to find out
which commit broke a build (in any Git repository), you can
use "git bisect" to tell Git which commit worked and which
commit failed, and Git will then run an arbitrary command
(e. g. "make && make check") to see which commit broke the
build.  (NB: Strictly speaking, this only works when the
failure is, eh, monotonous (?), i. e. the build worked for
all commits from last-good to the-one-before-first-failure
and failed for all commits from first-failure to now.)

In the context of build farms, you can make the command more
complex, e. g. set up a container/copy a VM template, ssh
into the instance and run "git checkout $commit && make &&
make check" there.

Tim




  parent reply	other threads:[~2020-12-20  6:54 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19 15:58 Multi-OS Emacs buildbot? Lars Ingebrigtsen
2020-12-19 16:27 ` dick.r.chiang
2020-12-19 17:49   ` Lars Ingebrigtsen
2020-12-19 18:43 ` Pankaj Jangid
2020-12-19 18:48   ` Lars Ingebrigtsen
2020-12-19 18:57     ` Yuri Khan
2020-12-19 19:01     ` Pankaj Jangid
2020-12-19 19:02       ` Lars Ingebrigtsen
2020-12-19 19:04         ` Lars Ingebrigtsen
2020-12-19 19:15           ` Pankaj Jangid
2020-12-19 19:18             ` Lars Ingebrigtsen
2020-12-20  2:35               ` Pankaj Jangid
2020-12-20  4:17                 ` Thien-Thi Nguyen
2020-12-20  5:16                   ` Pankaj Jangid
2020-12-20  6:54                 ` Tim Landscheidt [this message]
2020-12-20  8:17                   ` Pankaj Jangid
2020-12-20  8:56                     ` Thien-Thi Nguyen
2020-12-20 10:10                       ` Pankaj Jangid
2020-12-20 20:44                     ` Tim Landscheidt
2020-12-21  3:36                       ` Pankaj Jangid
2020-12-21  3:40                         ` Lars Ingebrigtsen
2020-12-21  5:58                           ` Pankaj Jangid
2020-12-20 13:58               ` Dmitry Gutov
2020-12-20 17:40                 ` Lars Ingebrigtsen
2020-12-20 18:03                   ` Dmitry Gutov
2020-12-20 18:08                     ` Lars Ingebrigtsen
2020-12-20 18:30                       ` Dmitry Gutov
2020-12-22  6:27                         ` Lars Ingebrigtsen
2020-12-22 12:01                           ` Dmitry Gutov
2020-12-19 19:27           ` Mising posts in thread from gwene Was: " Pankaj Jangid
2020-12-19 19:42             ` Lars Ingebrigtsen
2020-12-20  2:40               ` Pankaj Jangid
2020-12-19 19:10 ` Lars Ingebrigtsen
2020-12-19 21:45   ` 'make check' errors on Debian (was: Multi-OS Emacs buildbot?) Basil L. Contovounesios
2020-12-19 21:48     ` 'make check' errors on Debian Lars Ingebrigtsen
2020-12-20  6:39   ` Multi-OS Emacs buildbot? Richard Stallman
2020-12-20 17:30     ` Lars Ingebrigtsen
2020-12-19 20:16 ` Alan Third
2020-12-19 21:11   ` Lars Ingebrigtsen
2020-12-20  8:50     ` Michael Albinus
2020-12-20 14:04       ` Dmitry Gutov
2020-12-20 14:11         ` Michael Albinus
2020-12-20 17:32           ` Dmitry Gutov
2020-12-22  6:23             ` Toon Claes
2020-12-22 17:32               ` Michael Albinus
2020-12-23  7:11                 ` Lars Ingebrigtsen
2020-12-23  8:13                   ` Michael Albinus
2020-12-25 17:19                 ` Toon Claes
2020-12-25 17:34                   ` Michael Albinus
2020-12-25 19:40                   ` Lars Ingebrigtsen
2020-12-25 20:17                     ` Michael Albinus
2020-12-25 20:22                       ` Lars Ingebrigtsen
2020-12-25 20:38                         ` Michael Albinus
2020-12-25 20:43                           ` Lars Ingebrigtsen
2020-12-26  8:56                             ` Michael Albinus
2020-12-27  9:03                               ` Toon Claes
2020-12-27 10:01                                 ` Michael Albinus
2020-12-30 13:43                                   ` Toon Claes
2020-12-30 15:28                                     ` Alan Third
2020-12-31 14:14                                     ` Michael Albinus
2020-12-20 17:35       ` Lars Ingebrigtsen
2020-12-20 18:11         ` Michael Albinus
2020-12-22  6:28           ` Lars Ingebrigtsen
2020-12-19 20:20 ` Michael Albinus
2020-12-19 20:46 ` Daniel Martín
2020-12-19 21:12   ` Lars Ingebrigtsen
2020-12-22 15:37 ` Nikolay Kudryavtsev
2020-12-23  7:10   ` Lars Ingebrigtsen
2020-12-23 15:37     ` Eli Zaretskii

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=87czz5ynl9.fsf@passepartout.tim-landscheidt.de \
    --to=tim@tim-landscheidt.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).