From: Dmitry Gutov <dgutov@yandex.ru>
To: Toon Claes <toon@iotcl.com>, Michael Albinus <michael.albinus@gmx.de>
Cc: Ted Zlatanov <tzz@lifelogs.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: EMBA builds failing
Date: Sat, 20 Apr 2019 02:10:54 +0300 [thread overview]
Message-ID: <9e29960d-2cdb-87b6-31e7-398f548086b0@yandex.ru> (raw)
In-Reply-To: <87r29xequ6.fsf@iotcl.com>
On 19.04.2019 22:29, Toon Claes wrote:
> I also finalized the change to be included in GitLab Core, it will be
> available in GitLab 11.11:
> https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/27409
Terrific. That's certainly the best way to do this.
> I'm still seeing quite a number of timeout failures, so I upped the
> limit to 1h 30min. Hopefully that gives more reliable results.
Any ideas on the cause of the problem? In the jobs that I saw timeout,
it was pulling the aforementioned docker image.
But in the pipelines that run to completion, there's usually no mention
of gitlab-runner-helper at all in the log. Odd, isn't it?
> See https://emba.gnu.org/emacs/emacs/-/jobs/1430/raw
next prev parent reply other threads:[~2019-04-19 23:10 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e29960d-2cdb-87b6-31e7-398f548086b0@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.