From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pankaj Jangid Newsgroups: gmane.emacs.devel Subject: Re: Multi-OS Emacs buildbot? Date: Mon, 21 Dec 2020 09:06:25 +0530 Organization: Code Is Great Foundation Message-ID: <87r1nj6dae.fsf@codeisgreat.org> 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> <87wnxcxl5w.fsf@passepartout.tim-landscheidt.de> 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="12089"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Tim Landscheidt Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Dec 21 04:37:16 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 1krC0Z-00032d-Rm for ged-emacs-devel@m.gmane-mx.org; Mon, 21 Dec 2020 04:37:15 +0100 Original-Received: from localhost ([::1]:45520 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1krC0Y-0006PF-U5 for ged-emacs-devel@m.gmane-mx.org; Sun, 20 Dec 2020 22:37:14 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36224) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1krBzs-0005vK-Iz for emacs-devel@gnu.org; Sun, 20 Dec 2020 22:36:32 -0500 Original-Received: from mail-pl1-x62f.google.com ([2607:f8b0:4864:20::62f]:40230) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1krBzq-0002ue-PK for emacs-devel@gnu.org; Sun, 20 Dec 2020 22:36:32 -0500 Original-Received: by mail-pl1-x62f.google.com with SMTP id q4so4910397plr.7 for ; Sun, 20 Dec 2020 19:36:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codeisgreat-org.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:organization:references:mail-followup-to:date :in-reply-to:message-id:user-agent:mime-version :content-transfer-encoding; bh=CeNJRBgB8GV46J1rGV6u/AqPe7khJp84EVvbZx1I6t4=; b=UAcbNEdb6Sq0X4IW4iE//v1KhQ7iQdD8/vO61hW/Ypc/trUK5XTC3AEAVgHYHeDHUI CpIJ37QyWnkue8AHGIdn18oKyj5MdDms9rr9ZC3FohaNqaIbAfU2XYNKeQgakPU3c2lA XPwqJtThPNkBRk+LZ2joWL+fkpivLlzp7E9hcVm+EPZmCSP5fKkbC7pqrDVJQ/OBogUx yPTGsI1eJMfOft8QGS4tMwY6Hl+eqYC9p0Oo1pgQgmj6nUAgPKB56ACovpXIMi7ZpQpN xAE2yi66Hm1612xnhLt3UD+cDmfr4MbpwabjH3xNfKi8P/LwG4pRw8vgqG8rBy3fbYb2 rP7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:organization:references :mail-followup-to:date:in-reply-to:message-id:user-agent :mime-version:content-transfer-encoding; bh=CeNJRBgB8GV46J1rGV6u/AqPe7khJp84EVvbZx1I6t4=; b=EBjZiE697UJv0cEPem8Hal1wJADcrd3o6RRZdv6RJAmDcxOS6obhY/lDCzf7+yNsMg hl3ExDQ0AB6mTeA+7Bc8UwNVGWhSPW7rSW9i1+K5JmP2llqEXtWqzKPbEtdFtH3RbG/1 o9CVwM2GK2lOX+VvEWvMhGwslvdM/QjF/XpRrhO5KEpyTq3GVbZm50K186/vFwgYhPYn 4xVqFFGWalw5/cNREipBjbWwRajbLlzufal3Jby4BIUsuzTySInXxtJBsBNXQt6H6ePX F8XlHgmheVqvpYzmD0A8GHmO/ge/tjBmgcOURTxoAPQm91DZNcdBFuBK3wSTPbnnUhC2 8GJA== X-Gm-Message-State: AOAM533IdyyfexAIXtNbkBUmhnQM++3lBNbLj8HVKJ73qdbauHUFoBlu dGAs+VaZ/so2by7YT2T+CcrJqpF/x64G1A== X-Google-Smtp-Source: ABdhPJxpd1KTY+/QI8aSvdHIcjklWEwU3tNa4qG3fmnlwjsbxtvkTbAkCyyhY9khPTtWlZ/CEmtavw== X-Received: by 2002:a17:90a:de0f:: with SMTP id m15mr15653892pjv.207.1608521788842; Sun, 20 Dec 2020 19:36:28 -0800 (PST) Original-Received: from lt ([2405:201:5c06:70bb:a64e:31ff:fe0c:338c]) by smtp.gmail.com with ESMTPSA id c205sm14760613pfc.160.2020.12.20.19.36.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 20 Dec 2020 19:36:28 -0800 (PST) Mail-Followup-To: Tim Landscheidt , emacs-devel@gnu.org In-Reply-To: <87wnxcxl5w.fsf@passepartout.tim-landscheidt.de> (Tim Landscheidt's message of "Sun, 20 Dec 2020 20:44:11 +0000") Received-SPF: none client-ip=2607:f8b0:4864:20::62f; envelope-from=pankaj@codeisgreat.com; helo=mail-pl1-x62f.google.com X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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:261368 Archived-At: Tim Landscheidt 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=E2=80=99t 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, =E2=80=9C*this* particular commit has issues, do you= want to report a bug?=E2=80=9D. Of course, the later one covers only the platfor= ms 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.