unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Lars Ingebrigtsen <larsi@gnus.org>,
	 emacs-build-automation@gnu.org, emacs-devel@gnu.org,
	 Philipp Stephani <phst@google.com>
Subject: Re: broken "fast" build - hung containers
Date: Mon, 20 Sep 2021 13:53:39 +0200	[thread overview]
Message-ID: <87h7efea4c.fsf@gmx.de> (raw)
In-Reply-To: <y27tkm48.fsf@lifelogs.com> (Ted Zlatanov's message of "Sun, 19 Sep 2021 08:25:43 +0000")

Ted Zlatanov <tzz@lifelogs.com> writes:

Hi Ted,

> On Sat, 18 Sep 2021 23:13:51 +0200 Michael Albinus <michael.albinus@gmx.de> wrote:
>
>>> Could we disable the emacs-module-tests.el and process-tests.el inside
>>> EMBA Docker?
>
> MA> Sure. Our "make check" call shall be extended by (untested)
>
> MA> EXCLUDE_TESTS = %emacs-module-tests.el %process-tests.el
>
> I see you skipped the "fast" stage for now. That made the "normal" stage
> we do on every commit pass, but the full builds' "platform images"
> https://emba.gnu.org/emacs/emacs/-/jobs/28174 and "build images"
> https://emba.gnu.org/emacs/emacs/-/jobs/28144 stages are still failing
> on the master branch.

I will test in my private emba project what could be done.

> MA> If we do this, we shall also write bug reports for the maintainers of
> MA> both test files for analysis.
>
> I would really appreciate some guidance on increasing the verbosity of
> the tests so we can produce a bug report.

I believe there's no general rule. Every test package has its own
settings for increasing verbosity.

> There is no maintainer for either of those files. Based on the commit
> history it looks like Philipp Stephani is a good contact for the module
> tests and maybe could help us look at the process tests, so I am CC-ing
> Philipp.

Yep.

> I'd like to reboot the emba and emba-runner machines again to clear all
> the hung containers, but will wait in case there's some useful
> information in them for the debugging.
>
> Thanks
> Ted

Best regards, Michael.



      parent reply	other threads:[~2021-09-20 11:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a6kepd77.fsf@lifelogs.com>
2021-09-15  8:09 ` broken "fast" build - hung containers Lars Ingebrigtsen
2021-09-15  9:57 ` emba.el (was: broken "fast" build - hung containers) Michael Albinus
2021-09-16  8:31   ` emba.el Ted Zlatanov
2021-09-16 16:26     ` emba.el Michael Albinus
     [not found] ` <87fsu6p4bx.fsf@gmx.de>
2021-09-16 12:44   ` broken "fast" build - hung containers Ted Zlatanov
2021-09-16 16:16     ` Michael Albinus
2021-09-18 20:01       ` Ted Zlatanov
2021-09-18 21:13         ` Michael Albinus
2021-09-19  8:25           ` Ted Zlatanov
2021-09-19 14:49             ` Lars Ingebrigtsen
2021-09-20 11:53             ` Michael Albinus [this message]

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=87h7efea4c.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-build-automation@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=phst@google.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).