From: Ted Zlatanov <tzz@lifelogs.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
emacs-devel@gnu.org, dick.r.chiang@gmail.com,
Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: EMBA status
Date: Mon, 13 Sep 2021 13:09:21 +0000 [thread overview]
Message-ID: <zgsgpqpq.fsf@lifelogs.com> (raw)
In-Reply-To: <87r1dtrdpq.fsf_-_@gmx.de> (Michael Albinus's message of "Sun, 12 Sep 2021 17:54:57 +0200")
On Sun, 12 Sep 2021 17:54:57 +0200 Michael Albinus <michael.albinus@gmx.de> wrote:
MA> [Redirecting to emacs-devel@gnu.org]
MA> Lars Ingebrigtsen <larsi@gnus.org> writes:
>>> And yes, we're hurting without a modern CI.
>>
>> Indeed. Which reminds me -- what's going on with EMBA? It fails on all
>> builds:
>>
>> https://emba.gnu.org/emacs/emacs/-/pipelines
>>
>> "There has been a runner system failure, please try again"
MA> I'm kind of blocked on EMBA. I've asked Ted a while ago to give me
MA> access to the runner(s) for test projects; unfortunately I didn't get an
MA> answer.
I replied to Michael privately, but if anyone else wants to set up a
private fork and use the shared runner, please ping me.
I'm not sure how to resolve the wider problem of contributions that
break tests. It's easy to start sending blame-mails but it's equally
easy for people to ignore them.
Ted
next prev parent reply other threads:[~2021-09-13 13:09 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 ` Ted Zlatanov [this message]
2021-09-13 20:31 ` EMBA status Dmitry Gutov
2021-09-14 11:17 ` Lars Ingebrigtsen
2021-09-14 15:25 ` Alan Third
2021-09-14 19:16 ` EMBA status, " Ted Zlatanov
2021-09-15 8:05 ` 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=zgsgpqpq.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).