From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.devel Subject: Re: filenotify-tests.el failing inside Docker debian:stretch Date: Wed, 02 Jan 2019 15:31:18 +0100 Message-ID: <87r2dv3zd5.fsf@gmx.de> References: <87va37sbo6.fsf@gmx.de> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1546439402 11403 195.159.176.226 (2 Jan 2019 14:30:02 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 2 Jan 2019 14:30:02 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 02 15:29:58 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gehWv-0002qF-Uc for ged-emacs-devel@m.gmane.org; Wed, 02 Jan 2019 15:29:58 +0100 Original-Received: from localhost ([127.0.0.1]:45180 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gehZ2-00033V-Sz for ged-emacs-devel@m.gmane.org; Wed, 02 Jan 2019 09:32:08 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:54494) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gehYV-0002jx-Us for emacs-devel@gnu.org; Wed, 02 Jan 2019 09:31:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gehYS-0000Da-CU for emacs-devel@gnu.org; Wed, 02 Jan 2019 09:31:35 -0500 Original-Received: from mout.gmx.net ([212.227.17.22]:41547) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gehYS-0008Sl-2j for emacs-devel@gnu.org; Wed, 02 Jan 2019 09:31:32 -0500 Original-Received: from detlef.gmx.de ([213.220.145.106]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MYwQh-1gshme0Zal-00VkeG for ; Wed, 02 Jan 2019 15:31:19 +0100 In-Reply-To: (Ted Zlatanov's message of "Wed, 02 Jan 2019 14:16:25 +0000") X-Provags-ID: V03:K1:N30M3CIPkhGpjHgNEkkC1shRzgJ1u+co8Xyly9Oh7FiRcCdc3Ec alReVgsVjOkMZq47zwPRfeZx1hcCpBEJjbbqbrEd9N02Bbfyjv6r7fXTCXWmyWvA/xjoa6t caOpl7AdD2wpqrdan7ecZiusaTZj1+qm2X72t+BsWxyyWHxTsv8q2COU+yrMPmXYGBDZUd1 LiALKkv0epDp1FBHiBidQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:PdoZumFV/7I=:v+XawvmzGbqsqcn8Wbp5az gNkPdQzr+hQ0N2w8PYpIvhe6tNyQZyWLJP/i7dzi2Ge4tPLLK5JpchHWeZxkaF+mzGjs0YehK TpmjhCclyj/Qewpaj2s/Swxil0nPUj62T+AlmF1jqY8JD3GKMy2+L8QPhyKOeINfU7EqdPJ4L U0ZphmxxfrYvyooMrKi6rm8/TOuWGect8oRKDLFkkvCLrKq3Sc0xIcJQqN6T+u7eLQcnpkzJ+ 65mwxM/An6g5iJQb3L2HeXPjPoPYQnhEFygs+bkPSwhDHCOzKy5d/61gK3l4t/GNIzjNulKfp H4rjhyVVp7oXVU8OJyZR1xYXp2shRYxLmqs1bSrJjqy+9cVJnsJSMlcvSdcvjseMU1QCd22vp iI+zlWm0dPjcoWoeEHpvPaKbzX9WgNRkB+enq72wKvsmRvbi4HcH6udzqTrc1sBue0Xy7IEPQ oO5C0k0S+PO1xikiJTmWUhdy+b3OPj4z3Yh+fOuITFlIF7wAjMZsvYAWLX4Uuhcp/P8KjYBUW 5F1VtHSzfG26B9A7D9ZpUjrJVeeSz4AqZm4Hv0ihX3pjxR+p3gZQdLyWv+1Xtloit1mYBh8Nm a8+/PzJSafJy2WtOrBFXnzFGoKTrDhAbdy6vA5793MQq89K5Ws0GCbasTWloXLCJY0ywlviSo /FSq7h0Cx3HiKiR+W1DzJ1vk9aoMnDOYnhUQH3S1mJXVe4ZkydTZbM+8cqrUd/X6TmG8RPwTY DCAb3DgJ7Q6n9wyQ9IwS2H5dh8EGzs4nTalEJ1/OC/euRMALvwl2jAI3xvDdAYpqlc3KyThT X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 212.227.17.22 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:232084 Archived-At: Ted Zlatanov writes: Hi Ted, > 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. Yes, but pls use the variable name EMACS_EMBA_CI > But if this is a Docker issue, should we disable these tests in Docker > for everyone? I don't know whether this is a docker issue. First, I need some tests. > Ted Best regards, Michael.