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: Sun, 20 Dec 2020 13:47:46 +0530 Organization: Code Is Great Foundation Message-ID: <87tusgnb6d.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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33362"; 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 Sun Dec 20 09:18:28 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 1kqtv9-0008bz-DP for ged-emacs-devel@m.gmane-mx.org; Sun, 20 Dec 2020 09:18:27 +0100 Original-Received: from localhost ([::1]:52130 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kqtv8-0008DS-Ee for ged-emacs-devel@m.gmane-mx.org; Sun, 20 Dec 2020 03:18:26 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59266) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kqtub-0007mR-Iz for emacs-devel@gnu.org; Sun, 20 Dec 2020 03:17:53 -0500 Original-Received: from mail-pl1-x62e.google.com ([2607:f8b0:4864:20::62e]:41790) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kqtuZ-00045i-0Y for emacs-devel@gnu.org; Sun, 20 Dec 2020 03:17:53 -0500 Original-Received: by mail-pl1-x62e.google.com with SMTP id y8so3968005plp.8 for ; Sun, 20 Dec 2020 00:17:50 -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; bh=4HAUqU6Z+E5NwRkp9+Qi/m68MFWQ88/MdvZERTersrU=; b=tmpgYnBmls3jvGCAmOyjFRNA9t6YIr9Cm6eti6moEEmkseZ2+1sYlq9kNXG0EWtlXH /+RsfDXmQ4VXzfoPZ18UszlxyO8jNEchkUpZW4Y6duvZmiri4bz/lkLx4j8itL8eomff MzlTN8N8+Y5gGhEGB2NV1/MTgpqzOAQ/lcAdBkwssIP3IY7hx+cWMFk+iO1QBYns9WV7 wsndH6DMAb2Wq+yYkovTImEpJ465CHU+vAxQbgkhUzqXJ5Vi+tnNlbmCOpW/rfayDQQM SYu3c2QDmApO5Ng9aZXaG0GDJvnxKawxKBCTrA+YjAKCKMDEqp9aiXf9hLdr+9DxQIu4 LIrQ== 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; bh=4HAUqU6Z+E5NwRkp9+Qi/m68MFWQ88/MdvZERTersrU=; b=dhekKrJsdHWfQx/IpEH9SEvzlproRdfcnVdbCRJXHaCqiR8mEFx2FSqqgUFBLY/RjM tt+Bfdy3Qf9SwRk5rRb6IuanZi4yBoIgw1uwLJSn9GC8HAmyejX5mh/WsrxE8dQdTvBd GKYNvom9LBIRXa8zD4w9ver7NyLNjqR9Fls3Vyf8Ss6doUvuF+e5CHURtKXfDMc7ZDTX MgYD7XpatxLlhSJoT8ALossZf+tD41jm8PHDVE2aW4/538XPD6+8z/WEAW37P2xvVUd8 px5sG5PJUu1MvLPcWLwdqu3g/4Hlyr3M+Hulmk0d/ahfRqbJ9VZvplX8SsJ31CHejI3b rR6Q== X-Gm-Message-State: AOAM5333/R3Awqxv9izIccpvjnzL9mvINqnLvFzk7M3aPfcBQPNMo8ts zUZBtnhFtV0o6LpAvsEKhaflHUhSNmKctQ== X-Google-Smtp-Source: ABdhPJzjNNd5IOgCLQWLR4CXX8totR2ooTROp2e07GyxqYaXK9+NvLvNm08EVbvq/1uJzsBYoJXlxg== X-Received: by 2002:a17:90a:f3c5:: with SMTP id ha5mr12116890pjb.61.1608452269084; Sun, 20 Dec 2020 00:17:49 -0800 (PST) Original-Received: from lt ([2405:201:5c06:70bb:a64e:31ff:fe0c:338c]) by smtp.gmail.com with ESMTPSA id 6sm12969156pfj.216.2020.12.20.00.17.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 20 Dec 2020 00:17:48 -0800 (PST) Mail-Followup-To: Tim Landscheidt , emacs-devel@gnu.org In-Reply-To: <87czz5ynl9.fsf@passepartout.tim-landscheidt.de> (Tim Landscheidt's message of "Sun, 20 Dec 2020 06:54:10 +0000") Received-SPF: none client-ip=2607:f8b0:4864:20::62e; envelope-from=pankaj@codeisgreat.com; helo=mail-pl1-x62e.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:261314 Archived-At: Tim Landscheidt writes: >> 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. That might be useful if Git already has the information about good and bad commits. It helps in narrowing down problems. > (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. > 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. As Lars asked/said, not sure if that is of any help to us.