[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: filenotify-tests.el failing inside Docker debian:stretch
From: |
Ted Zlatanov |
Subject: |
Re: filenotify-tests.el failing inside Docker debian:stretch |
Date: |
Wed, 02 Jan 2019 14:16:25 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
On Wed, 02 Jan 2019 09:31:37 +0100 Michael Albinus <address@hidden> wrote:
MA> I would like to instrument the tests. In order to not annoy everybody,
MA> it would be great if there would be an indication, that a test runs on
MA> emba.gnu.org. Would it be possible to set an environment variable there,
MA> say $EMACS_EMBA_CI? Then I could wrap my instrumentation code inside
MA> (when (getenv "EMACS_EMABA_CI")
MA> ...)
MA> This is similar to the environment of hydra.nixos.org, where I could
MA> test for $EMACS_HYDRA_CI.
Of course, yes. This is simply added under `stage: test` in .gitlab-ci.yml:
variables:
IN_CI: 1
I would just make a branch with the test fix that also changes
.gitlab-ci.yml, and that should pass.
But if this is a Docker issue, should we disable these tests in Docker
for everyone?
Ted
- Re: filenotify-tests.el failing inside Docker debian:stretch, Michael Albinus, 2019/01/02
- Re: filenotify-tests.el failing inside Docker debian:stretch,
Ted Zlatanov <=
- Re: filenotify-tests.el failing inside Docker debian:stretch, Michael Albinus, 2019/01/02
- Re: filenotify-tests.el failing inside Docker debian:stretch, Ted Zlatanov, 2019/01/02
- Re: filenotify-tests.el failing inside Docker debian:stretch, Michael Albinus, 2019/01/02
- Re: filenotify-tests.el failing inside Docker debian:stretch, Ted Zlatanov, 2019/01/02
- Re: filenotify-tests.el failing inside Docker debian:stretch, Michael Albinus, 2019/01/03
- Re: filenotify-tests.el failing inside Docker debian:stretch, Ted Zlatanov, 2019/01/03