unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 13:08:20 +0200	[thread overview]
Message-ID: <87ilya5s2j.fsf@gnus.org> (raw)
In-Reply-To: <87bl424fc4.fsf@gmx.de> (Michael Albinus's message of "Wed, 06 Oct 2021 12:28:43 +0200")

Michael Albinus <michael.albinus@gmx.de> writes:

> Done. Since you act as guinea pig, pls report what isn't clear.

Thanks, it helps -- the main mystery was perhaps 

+Jobs in the 'build-images' and 'normal' stages are triggered by
+changes of respective files in the Emacs git repository.  All other
+jobs run scheduled in a pipeline every 8 hours.

so we normally get the failing native-comp job way down the screen, and
lots of successful builds after that at the top of the screen.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-10-06 11:08 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
2021-10-06  8:05       ` Michael Albinus
2021-10-06 10:28         ` Michael Albinus
2021-10-06 11:08           ` Lars Ingebrigtsen [this message]
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=87ilya5s2j.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).