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 06:54:10 +0000 Organization: http://www.tim-landscheidt.de/ Message-ID: <87czz5ynl9.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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12449"; 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 Cancel-Lock: sha1:es2Ro/PhRV4+fyGIA45tMn8QkxA= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 20 07:54:50 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 1kqscE-0003AN-CZ for ged-emacs-devel@m.gmane-mx.org; Sun, 20 Dec 2020 07:54:50 +0100 Original-Received: from localhost ([::1]:52126 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kqscD-0007Dm-FW for ged-emacs-devel@m.gmane-mx.org; Sun, 20 Dec 2020 01:54:49 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48552) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kqsbj-0006oz-Ag for emacs-devel@gnu.org; Sun, 20 Dec 2020 01:54:19 -0500 Original-Received: from ciao.gmane.io ([116.202.254.214]:40412) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kqsbh-0005JU-Ju for emacs-devel@gnu.org; Sun, 20 Dec 2020 01:54:19 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1kqsbe-0002b8-Qu for emacs-devel@gnu.org; Sun, 20 Dec 2020 07:54:14 +0100 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no 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:261311 Archived-At: Pankaj Jangid 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