unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Toon Claes <toon@iotcl.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Ted Zlatanov <tzz@lifelogs.com>, Dmitry Gutov <dgutov@yandex.ru>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: EMBA builds failing
Date: Fri, 19 Apr 2019 21:29:37 +0200	[thread overview]
Message-ID: <87r29xequ6.fsf@iotcl.com> (raw)
In-Reply-To: <87tvey481t.fsf@gmx.de> (Michael Albinus's message of "Tue, 16 Apr 2019 11:24:14 +0200")

[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]

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

> It still doesn't work. I'm getting emails with the link
>
> Job #1378 ( https://emba.gnu.org/emacs/emacs/-/jobs/1378 )

Ah, the Ansible playbook I ran didn't restart GitLab after patching. The
link should be good now.

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

I'm still seeing quite a number of timeout failures, so I upped the
limit to 1h 30min. Hopefully that gives more reliable results.

Although the latest failure on master seems to be legit:
See https://emba.gnu.org/emacs/emacs/-/jobs/1430/raw

> SUMMARY OF TEST RESULTS
> -----------------------
> Files examined: 212
> Ran 3102 tests, 2981 results as expected, 1 unexpected, 120 skipped
> 1 files contained unexpected results:
>   lisp/progmodes/flymake-tests.log
> Makefile:313: recipe for target 'check-doit' failed
> make[2]: *** [check-doit] Error 1
> make[2]: Leaving directory '/builds/emacs/emacs/test'
> Makefile:288: recipe for target 'check-expensive' failed
> make[1]: *** [check-expensive] Error 2
> make[1]: Leaving directory '/builds/emacs/emacs/test'
> Makefile:962: recipe for target 'check-expensive' failed
> make: *** [check-expensive] Error 2
> ERROR: Job failed: exit code 1


-- Toon



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-04-19 19:29 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 [this message]
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=87r29xequ6.fsf@iotcl.com \
    --to=toon@iotcl.com \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    --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).