Re: broken "fast" build - hung containers

[Ted Zlatanov]

On Wed, 15 Sep 2021 11:37:22 +0200 Michael Albinus <michael.albinus@gmx.de> 
wrote: 

MA> Ted Zlatanov <tzz@lifelogs.com> writes:

>> The "fast" EMBA build seems to be hanging. The normal one works. Seems
>> to be here:
>> 
>> https://emba.gnu.org/emacs/emacs/-/jobs/27726
>> 
>> ELC      src/emacs-module-tests.elc
>> GEN      src/emacs-module-tests.log
>> ERROR: Job failed: execution took longer than 3h0m0s second
>> 
>> I see two of them hanging right now (the docker containers have not been
>> removed). This probably is what started the cascade of failures that
>> broke EMBA.
>> 
>> I'll investigate when able, but if anyone has ideas, please let us know.

MA> I believe we shall comment out the "fast" jobs ATM. A while ago, I've
MA> tried to reorganize the jobs, maybe I have broken some dependencies. And
MA> honestly, I don't believe that the "fast" jobs bring something we don't
MA> see in the "normal" jobs. But that's another discussion ...

The specific jobs are below. The second and third one work.

test-fast-inotify hangs the Docker container (it can't be force-removed
by `docker rm' and when I try to remove the files, after stopping the
Docker daemon, I get a shm lock error). I think we should fix it rather
than disabling it. I have those hanging containers right now - what can
I do to find the trouble point?

test-fast-inotify:
  stage: fast
  extends: [.job-template, .test-template]
  variables:
    target: emacs-inotify
    make_params: "-C test check"

test-lisp-inotify:
  stage: normal
  extends: [.job-template, .test-template]
  variables:
    target: emacs-inotify
    make_params: "-C test check-lisp"

test-lisp-net-inotify:
  stage: normal
  extends: [.job-template, .test-template]
  variables:
    target: emacs-inotify
    make_params: "-C test check-lisp-net"

On Wed, 15 Sep 2021 10:09:10 +0200 Lars Ingebrigtsen <larsi@gnus.org> wrote: 

LI> Hm...  that seems vaguely familiar.  I think I've seen that before once.

LI> What's EMBA doing in the normal build here?  Is it just a "make check"?

Yeah. We don't do much unusual here, and it definitely used to work when
we set EMBA up. The underlying Docker image is the same between all
three jobs.

Thanks!
Ted