From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tim Landscheidt Newsgroups: gmane.emacs.devel Subject: Re: Multi-OS Emacs buildbot? Date: Sun, 20 Dec 2020 20:44:11 +0000 Organization: http://www.tim-landscheidt.de/ Message-ID: <87wnxcxl5w.fsf@passepartout.tim-landscheidt.de> References: <871rfliy8h.fsf@gnus.org> <87k0tdr60h.fsf@codeisgreat.org> <871rflhbsq.fsf@gnus.org> <87czz5r56v.fsf@codeisgreat.org> <87tushfwkv.fsf@gnus.org> <87pn35fwhv.fsf@gnus.org> <875z4xr4j2.fsf@codeisgreat.org> <87h7ohfvtx.fsf@gnus.org> <871rfl9pd4.fsf@codeisgreat.org> <87czz5ynl9.fsf@passepartout.tim-landscheidt.de> <87tusgnb6d.fsf@codeisgreat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33316"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 20 21:44:52 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kr5ZU-0008ZM-KV for ged-emacs-devel@m.gmane-mx.org; Sun, 20 Dec 2020 21:44:52 +0100 Original-Received: from localhost ([::1]:50544 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kr5ZT-0001Fh-MQ for ged-emacs-devel@m.gmane-mx.org; Sun, 20 Dec 2020 15:44:51 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57350) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kr5Yy-0000qQ-L6 for emacs-devel@gnu.org; Sun, 20 Dec 2020 15:44:20 -0500 Original-Received: from andalucia.tim-landscheidt.de ([2a01:4f8:1c1c:d4d0::1]:44470) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kr5Yw-0002G9-GP for emacs-devel@gnu.org; Sun, 20 Dec 2020 15:44:20 -0500 Original-Received: from dslb-090-186-106-166.090.186.pools.vodafone-ip.de ([90.186.106.166]:39406 helo=passepartout.tim-landscheidt.de) by andalucia.tim-landscheidt.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1kr5Yq-000823-55 for emacs-devel@gnu.org; Sun, 20 Dec 2020 21:44:12 +0100 In-Reply-To: <87tusgnb6d.fsf@codeisgreat.org> (Pankaj Jangid's message of "Sun, 20 Dec 2020 13:47:46 +0530") Received-SPF: pass client-ip=2a01:4f8:1c1c:d4d0::1; envelope-from=tim@tim-landscheidt.de; helo=andalucia.tim-landscheidt.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:261355 Archived-At: Pankaj Jangid wrote: > [=E2=80=A6] >> (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.) > My use-case is very simple. I pull and make bootstrap daily. And on some > odd day if the build breaks, I want to file a bug. If I have the > information which commit broke it then it helps the maintainers. Even if > the failure is monotonous (not sure what to call linear may be), that > may help in narrowing down the issue. It could be inaccurate but still. > [=E2=80=A6] 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 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.) Tim