From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Tim Landscheidt <tim@tim-landscheidt.de>
Cc: emacs-devel@gnu.org
Subject: Re: Multi-OS Emacs buildbot?
Date: Mon, 21 Dec 2020 09:06:25 +0530 [thread overview]
Message-ID: <87r1nj6dae.fsf@codeisgreat.org> (raw)
In-Reply-To: <87wnxcxl5w.fsf@passepartout.tim-landscheidt.de> (Tim Landscheidt's message of "Sun, 20 Dec 2020 20:44:11 +0000")
Tim Landscheidt <tim@tim-landscheidt.de> writes:
> Git records the changes to the local repository in a refer-
> ence log. One can access that with "git reflog" and/or "git
> rev-parse". (For example:
>
> | [tim@passepartout ~/src/emacs]$ git rev-parse 'HEAD'
> | 2d790c6c57b244447390c023679752243e0049c9
> | [tim@passepartout ~/src/emacs]$ git rev-parse 'HEAD@{one.week.ago}'
> | 2d790c6c57b244447390c023679752243e0049c9
> | [tim@passepartout ~/src/emacs]$ git rev-parse 'HEAD@{two.week.ago}'
> | 67a8bdb90c9b5865b7f17290c7135b1a5458c36d
> | [tim@passepartout ~/src/emacs]$
>
> suggests that I last fetched the Emacs repository some time
> between one and two weeks ago.)
>
> So, untested, if you encounter a bug in HEAD, you could
> start the bisection, mark that commit as "bad", then iterate
> over HEAD@{1}, HEAD@{2}, etc. marking failures as "bad" com-
> mits as you go along, until you find a working commit, mark
> that as "good", and then start "git bisect run".
I didn’t know git has a builtin system like this. We were probably on
the same page. I was doing it outside git. Building previous commits in
reverse order and recording somewhere. Thanks for sharing this.
> (I hope it is clear that I'm not advocating against using CI
> systems; I just want to point out how one can narrow down a
> bug if either a repository does not have a CI system attach-
> ed or the CI system was not configured to track a particular
> bug.)
The two approaches have different context. CI is a centralized approach
where commits are comming and the system points out a faulty one and
informs the maintainers. The other approach is distributed. So many
people are already pulling code and building on their systems. Probably
a script can ask them, “*this* particular commit has issues, do you want
to report a bug?”. Of course, the later one covers only the platforms
which are most used and leave out the others. Lars has discovered that
so many *BSD builds are failing. Only a centralized system will be
effective in such a case.
next prev parent reply other threads:[~2020-12-21 3:36 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
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 [this message]
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=87r1nj6dae.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=emacs-devel@gnu.org \
--cc=tim@tim-landscheidt.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).