[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: EMBA status, Re: EMBA status
From: |
Ted Zlatanov |
Subject: |
Re: EMBA status, Re: EMBA status |
Date: |
Tue, 14 Sep 2021 19:16:03 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
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