unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: Toon Claes <toon@iotcl.com>, Dmitry Gutov <dgutov@yandex.ru>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: EMBA builds failing
Date: Thu, 04 Apr 2019 08:40:49 +0200	[thread overview]
Message-ID: <87ftqyjmry.fsf@gmx.de> (raw)
In-Reply-To: <b2ae7c3a-c321-1272-b942-ff43f36f9fb6@yandex.ru> (Dmitry Gutov's message of "Thu, 4 Apr 2019 02:57:38 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

> Most of the recent builds have been failing with
>
>   execution took longer than 1h0m0s seconds
>
> and the log ending with
>
>   Pulling docker image gitlab/gitlab-runner-helper:x86_64-f100a208 ...

And while we are at this: the emails about failed jobs do not contain
the link to the raw log, again, so I stopped to check regularly. Could
we fix this problem forever? I don't know gitlab by heart, so I don't
know where to go.

> Thanks,
> Dmitry

Best regards, Michael.



  reply	other threads:[~2019-04-04  6:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 23:57 EMBA builds failing Dmitry Gutov
2019-04-04  6:40 ` Michael Albinus [this message]
2019-04-11 13:20 ` Dmitry Gutov
2019-04-11 13:26   ` Toon Claes
2019-04-11 13:31     ` Michael Albinus
2019-04-11 19:28       ` Toon Claes
2019-04-11 13:36     ` Dmitry Gutov
2019-04-16  7:07   ` Toon Claes
2019-04-16  9:24     ` Michael Albinus
2019-04-19 19:29       ` Toon Claes
2019-04-19 19:34         ` Michael Albinus
2019-04-20  9:16           ` Robert Pluim
2019-04-20 14:57             ` Paul Eggert
2019-04-20 19:18             ` Michael Albinus
2019-04-19 23:10         ` Dmitry Gutov
2019-04-23 10:21           ` Toon Claes
2019-04-22 20:36         ` Michael Albinus
2019-04-23 10:09           ` Toon Claes
2019-04-23 12:57             ` 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=87ftqyjmry.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=toon@iotcl.com \
    --cc=tzz@lifelogs.com \
    /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).