From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.devel Subject: Re: Multi-OS Emacs buildbot? Date: Sun, 20 Dec 2020 19:11:30 +0100 Message-ID: <87sg809wkt.fsf@gmx.de> References: <871rfliy8h.fsf@gnus.org> <878s9tfqma.fsf@gnus.org> <87k0tc3loz.fsf@gmx.de> <87r1nkcrd5.fsf@gnus.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="28810"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Alan Third , emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 20 19:12:55 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 1kr3CR-0007NV-4o for ged-emacs-devel@m.gmane-mx.org; Sun, 20 Dec 2020 19:12:55 +0100 Original-Received: from localhost ([::1]:58880 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kr3CQ-0005kx-7f for ged-emacs-devel@m.gmane-mx.org; Sun, 20 Dec 2020 13:12:54 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34910) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kr3BD-0005Ir-2o for emacs-devel@gnu.org; Sun, 20 Dec 2020 13:11:39 -0500 Original-Received: from mout.gmx.net ([212.227.17.21]:59753) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kr3BB-0006K5-28 for emacs-devel@gnu.org; Sun, 20 Dec 2020 13:11:38 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1608487892; bh=jq6y0BfsO4tevIIxAblgYZ902/gvu5i6vjgBuoiEtCE=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=NSpLyqjFkuj3gCO6+inB+/zLFov5BKVVu3pgi2ysNSLKEt0GRm2UD7GcOnQa+EIj3 wcDM6yEYmdpWVPxNyHlHez9bOeL/zPQeXnFYPQNFtiNTQD6N4Zs9V+sREP7TZrSs4l mgG2X3TpgVwca5i8AeaxN+K0ewO7vIKlIO63LtV0= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from gandalf.gmx.de ([212.86.52.107]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1Mof9F-1kJfEw3asj-00p4YT; Sun, 20 Dec 2020 19:11:31 +0100 In-Reply-To: <87r1nkcrd5.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 20 Dec 2020 18:35:50 +0100") X-Provags-ID: V03:K1:HfZxMwO4z1N8aauaa6OJNQt61g1UqaRsP7J2K0lNa/VL1nO/vOI DMbERXPR3VLpIXmc/4S0bs+uewURWjxCwZVUjTm9fZnv1PEeCJ23AUfsnZvne2jgUPDc3yZ ULLssQPpVQf3o79amYL0BRHevE6CXJLEGKNHXT80C5dAus5rXQb7Vodd1Xb8GjgXsgQoh9Y A3bjEtbTViDkRiWyk5sLw== X-UI-Out-Filterresults: notjunk:1;V03:K0:gZ8YMtPaNEQ=:MF9CCu1EoPBS0BclX48qWL YJnWhq9bv9EKsbPGF+VisjY1Flb26V35fH13llmjqh7iJXkK/BnJqBGiOSTl5KYS8Ad/LkydC 9gEPw+o7jN7Q9+BeAs9IaDIXRau9ah0QPsxzhMZi9TKKYUDBwi3nqIMHgROwlrbXtb3Y9Jj1J Vd47ePrd7poKsAFdfYIV79xpIHSPEvbbyh3GxJu3+91H+5NOIfzufEX0u4KiP4bKloFLKiKSy Ad8LqwjcTqDzM9VYhHRK338NPsfiFwe9jX4bjZ2BWhGIYzH7IDmhbIO4veRHDW5h90W2WIvdc ecuhYk4LAusK9IUbagclzzsgzhIhHGHp3HGICUZlApNYfXDcwuPhOeZCBv6UB3HaZc6+BHjb5 Xo50ByVjcNle41A1xn3R9rgVRz4Clm1aSoS5WJfSH76A0FKsDik4Hu386MhZ/avnw55YYb6IX x9FSxq4cUCr3p+6hRqOnM6uX3XWtglwwVGgmxp8f8KxjIDluI83Z8vewi16ggqNwABO1vch7a 6EXjPKjrHMUbUg1X1a35mvGd4w1HIFzenZl8xFrq/tgdvOcoT4cod0A+J7qt4tsTlxk8zfW2h iypiLXDPKSYUfB3yOTj4OKf+oLVO3cDxedXrV3aTPTvIG/ok5HhmfnzcRiEOrU0O+GByAtmsb p31onoVdBgDt3/WcBv9JRG60cA1e+4kVuQJjkkS72nfioJSijVFOJ5WfpjmviScFPFr0Py1Qk VNA4wVtQEhooGaft/Ffe+pKHtorZiSYHUMV1/JajE/qvRp+CuZm9QGtJb35wkefjEE6m3CAl Received-SPF: pass client-ip=212.227.17.21; envelope-from=michael.albinus@gmx.de; helo=mout.gmx.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, 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:261349 Archived-At: Lars Ingebrigtsen writes: Hi Lars, >> Maybe somebody will help you? I, for example, am already thinking >> about GitLab runners. But I didn't start to implement. > > The VMs are running on my machine on the desk over there *points*, so > I'm a bit leery of hooking them up to some external system that can > issue commands. Yes, it is also my concern. Well, I have a local OpenBSD VM, I also plan to do first tests installing a GitLab runner there. Just to get a feeling. Where to put such VMs afterwards is another story. Or you install a local GitLab instance in your environment, and let the CI jobs run there? >> Imagine, I have broken Tramp (not unlikely, you know). So I will get a >> message, and everybody who commits afterwards, would also get such >> message, until I have fixed this. Not so nice. >> >> AFAIK, GitLab has no memory. It doesn't remember, whether the previous >> job has failed. > > When I've worked with CI systems, they usually are pretty good at > assigning blame for a breakage? I'd be surprised if GitLab didn't have > such a basic feature. Maybe it has, and I don't know. I know just the trigger "pipeline is broken" and "pipeline is working"; GitLab sends the messages exactly when the trigger changes. For blaming^W informing *people*, we need a more fine-grained trigger. > But I know nothing about GitLab, and the > dashboard at emba isn't very encouraging -- it seems to say that most of > the builds failed because of git locking issues: > > ---- > Another git process seems to be running in this repository, e.g. > an editor opened by 'git commit'. Please make sure all processes > are terminated then try again. If it still fails, a git process > may have crashed in this repository earlier: > ---- > > So it looks like it needs some work? Yes, it needs some love. Likely this happens when there are too many commits in fast sequence; the resulting pipelines block each other. It is on my TODO to check what's up; perhaps I should give it more priority. Best regards, Michael.