From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 51025@debbugs.gnu.org
Subject: bug#51025: 28.0.50; comp-tests time out
Date: Wed, 06 Oct 2021 09:24:38 +0200 [thread overview]
Message-ID: <871r4yhayx.fsf@gnus.org> (raw)
In-Reply-To: <87y2764oha.fsf@gmx.de> (Michael Albinus's message of "Wed, 06 Oct 2021 09:11:13 +0200")
[-- Attachment #1: Type: text/plain, Size: 386 bytes --]
Michael Albinus <michael.albinus@gmx.de> writes:
> Meanwhile, the build of native-comp is failing on emba. See recent
> scheduled pipelines.
I just don't understand the emba interface, or what it's trying to say.
https://emba.gnu.org/emacs/emacs/-/pipelines
My guess is that "Passed" in green means that it didn't fail? And then
there's a "Failed" in red that's also "Scheduled".
[-- Attachment #2: Type: image/png, Size: 65006 bytes --]
[-- Attachment #3: Type: text/plain, Size: 141 bytes --]
So since the last master says "passed", I'd guess that things are fine?
But if I click that, it only has the pipelines cryptically called:
[-- Attachment #4: Type: image/png, Size: 8921 bytes --]
[-- Attachment #5: Type: text/plain, Size: 34 bytes --]
while the older, failed one has
[-- Attachment #6: Type: image/png, Size: 33013 bytes --]
[-- Attachment #7: Type: text/plain, Size: 194 bytes --]
In short, whenever I look at the emba pages, I have no idea what it's
trying to tell me.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-06 7:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 7:47 bug#51025: 28.0.50; comp-tests time out Michael Albinus
2021-10-05 17:46 ` Lars Ingebrigtsen
2021-10-06 7:11 ` Michael Albinus
2021-10-06 7:24 ` Lars Ingebrigtsen [this message]
2021-10-06 8:05 ` Michael Albinus
2021-10-06 10:28 ` Michael Albinus
2021-10-06 11:08 ` Lars Ingebrigtsen
2021-10-07 7:14 ` Michael Albinus
2021-10-08 11:47 ` Michael Albinus
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=871r4yhayx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=51025@debbugs.gnu.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).