From: Ted Zlatanov <tzz@lifelogs.com>
To: Alan Third <alan@idiocy.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
emacs-devel@gnu.org, Michael Albinus <michael.albinus@gmx.de>,
dick.r.chiang@gmail.com, Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: EMBA status, Re: EMBA status
Date: Tue, 14 Sep 2021 19:16:03 +0000 [thread overview]
Message-ID: <h7enotn0.fsf@lifelogs.com> (raw)
In-Reply-To: <87h7enwgmn.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 14 Sep 2021 13:17:36 +0200, Tue, 14 Sep 2021 16:25:07 +0100")
On Tue, 14 Sep 2021 13:17:36 +0200 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> I'm all for sending automatic mail from EMBA to the author of the
LI> failing commit, but I guess it has to be more reliable first.
Cool. Can we start with a month of monitoring
nntp+news.gmane.io:gmane.emacs.buildstatus and bugging people to fix the
build if it breaks? That should give everyone more confidence.
On Tue, 14 Sep 2021 16:25:07 +0100 Alan Third <alan@idiocy.org> wrote:
AT> On Tue, Sep 14, 2021 at 01:17:36PM +0200, Lars Ingebrigtsen wrote:
>>
>> But wasn't the problem here that all builds fail?
AT> Indeed. It looks like the docker environment is broken in some way and
AT> has been for months:
AT> ERROR: Job failed (system failure): Error response from daemon: Conflict. The
AT> container name "/runner-2oEDrUT7-project-1-concurrent-1-build-4" is already in
AT> use by container
AT> "f46df44a43bee1f61a6ede2eac732a4e06eaa2094659f7ea23718f093d67bcc6". You have to
AT> remove (or rename) that container to be able to reuse that name.
AT> (executor_docker.go:726:0s)
I stopped checking after the builds kept failing for a few months. I
think the rest of the volunteers also dropped off.
I've recovered the machine and its dedicated runner now. The lockup was
due to shared memory exhaustion.
Please let us know at emacs-build-automation@gnu.org or
nntp+news.gmane.io:gmane.emacs.build-automation if you see more errors.
Ted
next prev parent reply other threads:[~2021-09-14 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87o890pn60.fsf@dick>
[not found] ` <ff897941-48ca-c3a8-4993-844ec4ae6bf6@yandex.ru>
[not found] ` <87y284o33g.fsf@gnus.org>
[not found] ` <54758131-0e0d-1c4e-bf99-b329688a1b8d@yandex.ru>
[not found] ` <8735qbmfqn.fsf@gnus.org>
2021-09-12 15:54 ` EMBA status (was: bug#50509: 28.0.50; [PATCH] elisp-mode-tests regression) Michael Albinus
2021-09-13 13:09 ` EMBA status Ted Zlatanov
2021-09-13 20:31 ` Dmitry Gutov
2021-09-14 11:17 ` Lars Ingebrigtsen
2021-09-14 15:25 ` Alan Third
2021-09-14 19:16 ` Ted Zlatanov [this message]
2021-09-15 8:05 ` EMBA status, " Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=h7enotn0.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=alan@idiocy.org \
--cc=dgutov@yandex.ru \
--cc=dick.r.chiang@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).